Skip to content

docs: clarify that resetting a user password must run on the coderd host #7845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 5, 2023
Merged

docs: clarify that resetting a user password must run on the coderd host #7845

merged 1 commit into from
Jun 5, 2023

Conversation

sharkymark
Copy link
Contributor

@sharkymark sharkymark commented Jun 5, 2023 •
edited
Loading

This PR:

  1. Addresses user experience friction where prospects and customers do not know how to reset a user's password. We have seen several inquiries where the context of running this command is misunderstood (it's a direct connect to PostgreSQL so must run on the coderd control plane)
  2. In particular, if an owner role-based user has to be reset on a Kubernetes deployment, adding an kubectl example. A current Coder customer ran into this problem today asking for help

This will eliminate inbound support questions that clog up Coder's support organization so that users can self-service and get unblocked.

image image

@sharkymark sharkymark requested review from ericpaulsen and bpmct June 5, 2023 12:52
@ericpaulsen ericpaulsen changed the title chore(docs): Add clarifying language that resetting a user password must run on the coderd host chore(docs): add clarifying language that resetting a user password must run on the coderd host Jun 5, 2023
@ericpaulsen ericpaulsen enabled auto-merge (squash) June 5, 2023 13:05
@matifali matifali changed the title chore(docs): add clarifying language that resetting a user password must run on the coderd host docs: clarify that resetting a user password must run on the coderd host Jun 5, 2023
@ericpaulsen ericpaulsen merged commit 88dc66a into main Jun 5, 2023
@ericpaulsen ericpaulsen deleted the docs-owner-role-reset-clarification branch June 5, 2023 13:37
@github-actions github-actions bot locked and limited conversation to collaborators Jun 5, 2023
@sharkymark
Copy link
Contributor Author

@matifali the nomenclature chore(docs) is what other senior engineers have told me to do.

@matifali
Copy link
Member

matifali commented Jun 5, 2023

Thanks, @sharkymark, for letting me know about this. I learned about this just now. I always get confused about when to use chore(docs) and when to use docs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@ericpaulsen ericpaulsen ericpaulsen approved these changes

@bpmct bpmct Awaiting requested review from bpmct

Assignees

@sharkymark sharkymark

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@sharkymark @matifali @ericpaulsen