Skip to content

Conversation

@joshlreese
Copy link
Contributor

Two new auth subcommands have been added:

  • activate-api-token: Accepts an API token either via stdin or a secure prompt and saves it in the OS keyring. This token will be used to obtain a token compatible with Datum Cloud infrastructure APIs when no service account credentials are located.
  • logout: Removes an activated token from the OS keyring.

Future work will likely come to clean up keyring access when we implement token caching or move from personal access tokens to alternative credential approaches.

We may also want to keep an eye on cli/cli#7743 to follow suit if a keyring library switch is made.

Two new auth subcommands have been added:

- activate-api-token: Accepts an API token either via stdin or a secure prompt and saves it in the OS keyring. This token will be used to obtain a token compatible with Datum Cloud infrastructure APIs when no service account credentials are located.
- logout: Removes an activated token from the OS keyring.

Future work will likely come to clean up keyring access when we implement token caching.

We may also want to keep an eye on cli/cli#7743 to follow suit if a keyring library switch is made.
@joshlreese joshlreese requested a review from scotwells December 29, 2024 01:57
@joshlreese joshlreese merged commit 4160e6a into main Dec 29, 2024
1 check failed
@joshlreese joshlreese deleted the feature/datum-os-auth branch December 29, 2024 20:49
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.

3 participants