-
Notifications
You must be signed in to change notification settings - Fork 71
Command to switch active user #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/assign |
hey! just trying to figure out if I understand it. Does this : harbor login <server address> -u <username> -p <password> already not suffice the requirement? |
When you have already saved your credentials once, there is no need to enter password again and again. Similar to how you can have multiple accounts on a website and switch accounts without having to enter your password again and again |
Gotcha. I believe we have to be really careful about security when implementing this. Since harbor allows RBAC, logging in without passwords could be tricky. Let me know what you guys think. |
I would suggest using harbor config switch. @Darkhood148 |
I was thinking of a simpler approach. Search for the username in the config, if it doesn't exist, throw an error. If it exists, prompt the user to select the |
IMO Harbor config switch isn't clear. It misses the what... My suggestion would be context Let then user select based on context name. |
We had this discussion already in this issue: #275 IMHO, introducing a |
thank you for pointing that out. While Before moving forward, we should agree on the one single option! |
Yes, I think it should like this. we can use
Because harbor config in future can grow into more different options. |
We should also document this |
Sounds great. I can start working on it. |
Issue:
harbor login
is used to add new credentials toconfig.yaml
and switch to the newly added credentials. However there is no command to switch between already added credentials.Solution:
Add a new command:
This command will switch to the credentials with the username that is provided; given it is available in the
config.yaml
The text was updated successfully, but these errors were encountered: