currently, POST /deployment/token is used for both creating the token and refreshing it.
To avoid users accidentally refreshing a valid token (and having to change it wherever they use it), we should separate refreshing the token to use PUT, then make changes in cli the to create a separate update or refresh subcommand, add a confirmation prompt before overwriting an existing token, etc.
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| cli: Improve deploy-token command UX and safety | repos/cloud/toolforge/components-cli!6 | sstefanova | slavina/refresh-token | main | |
| deploy-token: split create/refresh into POST/PUT endpoints | repos/cloud/toolforge/components-api!43 | sstefanova | slavina/refresh-token | main |
sstefanova opened https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/43
deploy-token: split create/refresh into POST/PUT endpoints
sstefanova merged https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/43
deploy-token: split create/refresh into POST/PUT endpoints
group_203_bot_4866fc124f4b41659f667468a6115cf3 opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/629
components-api: bump to 0.0.71-20241129083321-0a425581
sstefanova opened https://gitlab.wikimedia.org/repos/cloud/toolforge/components-cli/-/merge_requests/6
cli: Improve deploy-token command UX and safety
sstefanova merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/629
components-api: bump to 0.0.71-20241129083321-0a425581
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/components-cli/-/merge_requests/6
cli: Improve deploy-token command UX and safety