You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(cli): make templates push support every templates create flag so create can be removed #31998
coder templates create was deprecated in #11390 in favor of coder templates push plus coder templates edit. push still can't replace create, though: create sets these template settings when it creates the template, and push has no flags for them.
All other create flags are also in push. The API already supports every one of these settings: CreateTemplateRequest and UpdateTemplateMeta (which treats nil as "leave unchanged") both have the fields. So this is CLI-only work, with no API or database changes.
Work shared by all of them
Flag definitions.create and edit each define these options separately, with different descriptions. A shared templateSettingsFlags struct, like the existing templateUploadFlags, would make each flag a small change and keep the three commands consistent.
Updating an existing template.push also updates existing templates, so it should only send flags the user actually set (`userSetOption`). Otherwise it would reset settings that someone changed in the UI. Today push only patches template metadata inside `case activate:`. We need to decide whether settings flags still apply with --activate=false.
License checks. The AGPL schedule store keeps the old values without an error for licensed settings, so the CLI has to check entitlements first. create (L50) and edit (L63) each do this check in their own code. A shared helper would avoid a third copy.
Generated files. Regenerate cli/testdata/coder_templates_push_--help.golden and docs/reference/cli/templates_push.md (make gen).
After everything lands, remove coder templates create.
Estimated scope
In total, this is about 150 to 300 lines including tests, all in cli/. If the shared flag struct is done first, each flag is mostly one field in the create request, one optional field in the update request, and a test.
Activity
linear-code commentedon Nov 10, 2026
ENG-3523