Improve tiger auth status output#106
Merged
Merged
Conversation
…status' table output
murrayju
reviewed
Nov 19, 2025
Askir
approved these changes
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the CLI to hit the new
GET /public/api/v1/auth/infoendpoint, which returns information about the API key being used to access the API. This is useful for a variety of reasons:tiger auth statuscan now hit that API endpoint to verify the validity of the API key, instead of just reporting the presence of stored credentials (which might have been revoked, or became invalid for some other reason).tiger auth statusnow display significantly more information in its output, such as the name and public key of the credentials, the user who issued them, which project their associated with, etc. It also now supports the-o/--outputflag, which controls the output format (table,json, oryaml).tiger auth loginnow hits the endpoint to verify the validity of the credentials, instead of hitting some other random API endpoint.tiger auth loginalso uses the endpoint to get the project ID corresponding to the public and secret keys, which removes the need for the--project-id/TIGER_PROJECT_IDparameters when using the manual credentials flow (i.e. when not using the interactive OAuth login flow).tiger auth loginnow hits thePOST /public/api/v1/analytics/identifyendpoint to identify the user upon login. This associates a user ID and email address with future CLI events, making it easier to associate them with console events as well as to filter internal users out of analytics data.Closes AGE-125
Closes AGE-153
Closes AGE-247