-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
update-context is confusing with profiles #4049
Conversation
Can one of the admins verify this patch? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: RA489 If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cmd/minikube/cmd/update-context.go
Outdated
@@ -49,9 +49,9 @@ var updateContextCmd = &cobra.Command{ | |||
exit.WithError("update config", err) | |||
} | |||
if updated { | |||
console.OutStyle("celebrate", "IP has been updated to point at %s", ip) | |||
console.OutStyle("celebrate", "IP has been updated to point at %s", machineName) |
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.
This is still slightly confusing for me. How about:
"%s IP has been updated to point to %s, machineName, ip
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.
@tstromberg done
@minikube-bot OK to test |
Thank you! |
update-context is confusing with profiles: "IP was already configured"
fixes #3983