up login --profile=foo will update the profile foo or create it if it doesn't exist. However up profile set space --profile=foo will only update the existing profile, it won't create it. This is inconsistent and potentially confusing.
How can we reproduce it?
branden@crateria ~ % up profile list
CURRENT NAME TYPE ACCOUNT KUBECONFIG KUBECONTEXT
* default token branden
branden@crateria ~ % up profile set space --profile=space
up: error: profile.Cmd.AfterApply(): profile not found with identifier: space
branden@crateria ~ % up login --profile=cloud
3122e6b9-78c3-4264-995f-068364b00051 logged in
branden@crateria ~ % up profile list
CURRENT NAME TYPE ACCOUNT KUBECONFIG KUBECONTEXT
* cloud token branden
default token branden
branden@crateria ~ %
What happened?
up login --profile=foo
will update the profilefoo
or create it if it doesn't exist. Howeverup profile set space --profile=foo
will only update the existing profile, it won't create it. This is inconsistent and potentially confusing.How can we reproduce it?
What environment did it happen in?
v0.21.0