[FEATURE] Expire cli tokens.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 396
- Forks
- 83
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
It is annoying to use Doppler with remote servers or serverless services like Codespaces because I have to manually delete the CLI token every time (from the dashboard).
Describe the solution you'd like
There should be a way to define the token expiration time. Like doppler login -e 300
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 at the doppler login command entry point and trace how CLI tokens are created and removed. Determine where an expiration value such as -e 300 would need to be represented and enforced, then verify that an expired token can no longer be used and that the documented command behavior is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100