-
Notifications
You must be signed in to change notification settings - Fork 903
chore: create workspaces and templates for multiple orgs #13866
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
Conversation
4160118
to
d59cb83
Compare
401166d
to
da4d8ee
Compare
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.
I think this is all good for now, but before experimental release I'd like to nail down how much we need to handle different org cases or if we just make everything take a flag explicitly to simplify things. Something we should probably loop in with product.
The downside of the explicit flag is deployments with only 1 org 😢 |
What this does
This allows creating a workspace using a template in an organization other than the default. If only 1 organization exists, then nothing changes.
If you select a template that has a unique name, then
coder create
can infer the organization to create the workspace in. If the template name is not unique across organizations, then using--org
is required.Changes
Create lists templates
template create
(deprecated command, but still exists)Prints out the coder cli command to use the template without any ambiguity. If another template of the same name exists in another org,
--org=<org_name>
must be specified.coder create
with ambiguous organizationIf a template name is not unique across multiple organizations,
coder create
requires a--rg=<org_name>
flag to disambiguate.coder create
with a wrong organization selectedIf you try to use a template with
--org
set to the wrong organization, an error is thrown.