Bug 1471160
Summary: | use current context when logging in | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Aleksandar Kostadinov <akostadi> |
Component: | oc | Assignee: | Juan Vallejo <jvallejo> |
Status: | CLOSED WONTFIX | QA Contact: | Xingxing Xia <xxia> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.1 | CC: | aos-bugs, jokerman, jvallejo, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-10-25 18:09:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Aleksandar Kostadinov
2017-07-14 14:31:06 UTC
I think a solution to this would be to have the `oc login` command acknowledge the global `--context` flag (if one is provided). That way, if it is a user's intent to actually have the default context with a default name be created on login, the command's current behavior remains unchanged. Origin PR: https://github.com/openshift/origin/pull/16161 Provided that `oc` uses current context server for the login command, then it makes sense to update current context. I think it only makes sense to create a new context when user changes `server` or `user` when logging in. Although the idea behind this bug makes sense, it looks like we are not planning on allowing users to manage contexts via `oc login` [1]. 1. https://github.com/openshift/origin/pull/16161#issuecomment-328577474 Closing this bug for now. |