Skip to content

Make auth refresh more convenient with secure storage#7098

Merged
samcoe merged 1 commit intotrunkfrom
auth-refresh-secure-storage
Mar 7, 2023
Merged

Make auth refresh more convenient with secure storage#7098
samcoe merged 1 commit intotrunkfrom
auth-refresh-secure-storage

Conversation

@samcoe
Copy link
Contributor

@samcoe samcoe commented Mar 7, 2023

This PR adds some convenience functionality to auth refresh command. Now if a user logged in with auth login --secure-storage or auth refresh --secure-storage next time they use auth refresh the --secure-storage flag will be implicitly set. Basically, if the token we want to refresh is coming from secure storage we assume that the user wants to continue to use secure storage even if they forgot to add the --secure-storage flag.

@samcoe samcoe requested a review from a team as a code owner March 7, 2023 02:19
@samcoe samcoe self-assigned this Mar 7, 2023
@samcoe samcoe requested review from mislav and removed request for a team March 7, 2023 02:19
Copy link
Contributor

@mislav mislav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good; thanks.

Would we also consider supporting explicitly disabling via --secure-storage=false to quit storing in keyring and write the token to config file instead?

@samcoe
Copy link
Contributor Author

samcoe commented Mar 7, 2023

@mislav I wasn't not planning on supporting that flow. If the user wants to quit storing the token in the keyring using auth logout and then auth login would be the recommended path. I can see the value of just being able to do it in auth refresh but with the release looming I would suggest we hold off and perhaps add it before the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants