#2269 [FlyteCTL Feature] Introduce flytectl context Issue created by katrogan Describe the feature/command for FlyteCTL It's a common scenario to use flytectl to interact with different Flyte back-ends, for example sandbox and a hosted deployment or staging and production deployments. However, the experience is frustrating and difficult to debug with multiple authenticated back-ends. Currently flytectl stores one token in keychain which leads to `302`s when trying to use flytectl with another flyte host/back-end. Fixing this requires end-users to understand the cause of the 302, delete the token from keychain and re-initiate their requests to go through the auth flow. Provide a possible output or UX example Like kubectx, it would be useful to introduce flytectl contexts (

flytectx

maybe?) to manage different authenticated sessions and possibly flytectl configs and make switching between different flyte deployment environments seamless. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte