is there a chance to get rid of template create? I mean if I push a non existing template I want it to be created on the fly. Are there any technical reasons for this or could this behaviour be changed? UseCase is for BCM we have to ensure the installation is complete from zero. So after (re)-creation of coder deployment there is the last step to deploy the template(s) from a github workflow. If one can not push the template to coder if the template does not exists this would mean one have to go to CLI and create the template or we have to create the template on each push to the workflow.

There's no real reason we couldn't do this I suppose. Thoughts @Ben?

The only thing might be permission-wise. A template-admin of a certain can push but not create

I hope you don't mind me asking, but when you are talking about template create, do you mean the cli command or something else?

yes, this would be called in GitHub Action to promote templates to coder

So the cli wont change at all for now?

Ahh, good point @JanL! @KozmikNano we're discussing merging the two commands. It'd certainly still exist in the CLI!

Thank you. Although I would use GitHub for long-term deployments, I will definitely need the CLI to test and quickly push updates.

To me this sounds a good idea.

coder templates push <template-name>

should create a new template if it doesn't exist already.

I'd be concerned about making a typo in my command and getting a new template instead of updating an existing one. Maybe we could take inspiration from Helm's behaviour and add a

--create

parameter to

coder templates push

?

what is the difference between making a typo with or without

--create

parameter? In our use case it is not possible to have a typo as it gets executed in a GitHub action.

We are also thinking about the cli command

I think we should start with https://github.com/coder/coder/issues/6851

I have no issue 👍