Why did we allow changing version to begin with?

We should consider doing this per-template.

This caused confusion when this came in. I forgot to post something about it.

Would love to see this just go. There's no reason in our environment for someone to ever rollback a version. It's actually a risk.

Why did we allow changing version to begin with?

It's nice to "roll back" if a breaking change occurred in a template version. We never had a feature for this in v1 until very recently, because images were the source of truth and any user could add image tags.

However, I totally agree it should be disable-able for deployments who want to have stricter policies for workspaces.

Maybe instead of "change version" we should introduce a concept of tags. Then:

• Don't want rollbacks? Just deploy to template:master
• Want rollbacks? Just tag coder templates tag template:master template:last before every template update

Sounds fantastic to me :)

Maybe instead of "change version" we should introduce a concept of tags. Then:

• Don't want rollbacks? Just deploy to template:master
• Want rollbacks? Just tag coder templates tag template:master template:last before every template update.

#3775 is related in suggesting setting a message(description) on every push.

Also my comment on #6030 is related.

@bpmct

Closing in favor of #6635. We're definitely considering some form of tags/branches too