Doc Feedback: Long lived token for automated CI/CD process
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 33
- Forks
- 25
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 1
Description
Location : https://updates.docs.wso2.com/en/latest/updates/wso2-registry-cli-access/
For an automated CI/CD process customers will need a long term token, or a cli way to generate a new one on demand. Please update the document to indicate how they should approach this use case. IE: robot token
Contributor guide
No contributing guide indexed for this repository
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 with the document at https://updates.docs.wso2.com/en/latest/updates/wso2-registry-cli-access/ and review how tokens are currently described. Determine the documented approach for automated CI/CD, including a long-lived or robot token and any CLI-based renewal path. Done means the page clearly explains this use case to customers.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100