-
Notifications
You must be signed in to change notification settings - Fork 933
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
Support cf login -u
when targeting Korifi / Kubernetes
#2380
Conversation
This logic was formerly in the auth command, but this will allow for reuse in the login command. [cloudfoundry/korifi#2195] Co-authored-by: Dave Walter <walterda@vmware.com>
- Stop using `k8s-auth-info` for kubernetes prompts and credentials and use `username` instead. This allows the existing login code to work with korifi with fewer changes. - Remove support for menu-based prompts in login except for username. These menus are only used with korifi and only for the username. - Warn the user when they provide a password and are using korifi [cloudfoundry/korifi#2195] Co-authored-by: Dave Walter <walterda@vmware.com>
We ignore the password when authenticating against Kubernetes in both commands. [cloudfoundry/korifi#2195] Co-authored-by: Dave Walter <walterda@vmware.com>
Closed and reopened to trigger another run of the tests. It looked like there was an issue with the test infrastructure when we initially submitted it. |
Looks good to me. @a-b What do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We will observe the integration test run in V8 branch, since running tests off PR branches is now broken. |
Does this PR modify CLI v6, CLI v7, or CLI v8?
The PR modifies v8
Description of the Change
cf login -u
now works when authenticating against Kubernetes. It will warn if a password is provided. We added the same warning tocf auth
Why Is This PR Valuable?
It furthers support for Korifi by supporting more workflows
Why Should This Be In Core?
To further support integration with Korifi
Applicable Issues
cloudfoundry/korifi#2195
How Urgent Is The Change?
This change isn't urgent but merging sooner will avoid us needing to rebasing later
Other Relevant Parties
We aren't aware of any