-
Notifications
You must be signed in to change notification settings - Fork 887
Support multiple deployments (contexts) via Coder CLI #9857
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
Comments
Agree, we have a staging and prod deployment of Coder that our team maintains and it'd be great to have the ability to switch between the two. |
Any ETA for this feature!? 👀 |
@jpmh1309 not yet, but we've tinkered with it. It's extremely easy for us to implement, UX is just a bit odd. |
Some good discussion in #13325 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello Coders,
I would like to request to have the CLI feature to be able to login on multiple coders at the same time. Currently to SSH to a coder WS you will need to login to server, to create a token, and with that token it will grant you access to your WS SSh connection. But If you need to connect to other Coder WS, you will need to relog to new instance of coder, killing the login token of the first instance.
I had managed this error before by mapping on the config file {url1: token1, url2: token2}, and exposing a default server on CLI and a flag to override the location
-l server1
if needed.Let me know what you think about this approach.
PS: We run multi-arch K8s clusters, so depends on which cluster you run, you will have different capabilities
The text was updated successfully, but these errors were encountered: