Documentation of locking and unlocking Automate local users
Open
Nobody has claimed this yet.
Documentation
Status: Untriaged
Type: Docs Intake
- Dominant language
- HTML
- Stars
- 143
- Forks
- 438
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
General details
Link to page & section that needs updated:
Business group: (ex. product, engineering, marketing)
Product owner:
Team:
Date update needs to be published:
Product
Product
- Chef Automate
- Chef Habitat
- Chef Infra Client
- Chef Infra Server
- Chef InSpec
- Chef Workstation
- Other:________________
Update details
- Document how Automate local user is locked
- How an Admin can unlock a local Automate user
Existing resources
GitHub Repository:
Issue link(s): https://github.com/chef/automate/issues/4845
PR link(s):
AHA! link(s):
Other draft documentation:
Related design, business docs, or other information:
Review
Name of technical reviewer:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related Chef Automate issue #4845 and the existing Chef Automate documentation; no target file or page is named here. Done means documenting how a local Automate user becomes locked and how an Administrator unlocks that user.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100