Skip to content

Evaluate coder_workspace_tags during template create/push #15427

Closed
@bpmct

Description

@bpmct

The coder_workspace_tags data source is not respected or read from the template during template imports, but it works for template builds. As a workaround, the admin must run a generic provisioner simply for template imports AND/OR set tags manually in the template UI.

This is a bad workaround as certain provisioners must be run just for template imports. From #15047:

It's definitely a bug that we don't process coder_workspace_tags for template import jobs. A full fix would have us directly inspect the HCL on coderd to find the coder_workspace_tags and the coder_parameters, then resolve the tags based on the parameters passed to the import job.

Related PRs:

Metadata

Metadata

Assignees

Labels

must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.need-backendIssues that need backend work

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions