Add support for login command
#159
Merged
+691
−34
Conversation
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
…credentials in config file to perform further operations Signed-off-by: Harsh4902 <[email protected]>
Signed-off-by: Harsh4902 <[email protected]>
lbroudoux
added
kind/feature
lbroudoux
approved these changes
May 19, 2025
Member
lbroudoux
left a comment
lbroudoux
left a comment
There was a problem hiding this comment.
Looks All Good To Me!! Excellent! 🎉
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR adds support for the login command in our CLI tool.
It allows users to perform both password and sso based logins.
For
passwordbased login, users need to set theMICROCKS_CLIENT_IDandMICROCKS_CLIENT_SECRETenvironment variables. Then, they can enter their username and password interactively or use the--usernameand--passwordflags.ssobased login redirects users to their default web browser, where they can complete the login process. They can use the--sso-launch-browser=falseflag to get the authentication URI instead of being redirected to the browser.Each execution of the
logincommand creates a context for the given server and sets it as the current context.Related issue(s)
Resolves #154