oxidecomputer / oxidecomputer/omicron
Give access tokens a name field
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I'm tempted to make it optional, since a) any existing tokens will need to be given one, and b) you might not want to bother giving a name. On the other hand, nothing else with a name lets you leave it off. It would be convenient to make tokens behave like other API resources. Will have to think about it.
This is the lowest-priority part of the token work collected in #8138. It is not load-bearing.
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 reviewing the token work collected in #8138 and how existing API resources handle name fields. Resolve whether token names are required or optional, including how existing tokens receive names. Done means the naming behavior is decided and implemented consistently for access tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100