chore: deprecate template create command in favor of template push#11390
Conversation
|
I'm good with this change as it gets us closer to the ideal state. We will have to mark the PR as a breaking change. |
|
Great, I'll continue this one and mark it so. Thanks for the guidance on this one. |
|
@ammario One more thing, since this will be a breaking change - should we just bite the bullet and remove the create command altogether? Or is that too drastic? I figure it may be better than breaking people twice, once now and once again when we remove it. (And lets us do the cleanup now instead of possibly forgetting to do it later). |
|
That's a good point. We could go ahead and break "create" right now, but I don't think we should simply remove the command from the CLI as the error message would be scary. Instead, we can hide the subcommand and make it fail with something like "use |
|
Hmm, I wonder if we can just make |
|
I went ahead and just made the command produce an error instructing users to |
sreya
left a comment
There was a problem hiding this comment.
It would be good if the command was marked as deprecrated in the coder templates --help output
sreya
left a comment
There was a problem hiding this comment.
LGTM, may be good to support deprecation in clibase but I don't have any suggestions for the best way to do it
2cfd8df to
13794fd
Compare
Closes #9318
What this changes:
coder template createhas been marked as deprecated and produces a warning pushing users topushandeditcommands.--createflag has been removed frompushin favor of automatically creating if template does not exist.--privateflag has been added tocoder template editto meet parity with the previouscreatecommand flags.disable_everyone_group_accessbool has been added to the template edit API to support the new--privateflag.coder templates createtocoder templates push.Examples: