@@ -17,6 +17,7 @@ specified:
17
17
``` tf
18
18
data "coder_workspace_tags" "custom_workspace_tags" {
19
19
tags = {
20
+ "az" = var.az
20
21
"zone" = "developers"
21
22
"runtime" = data.coder_parameter.runtime_selector.value
22
23
"project_id" = "PROJECT_${data.coder_parameter.project_name.value}"
@@ -50,6 +51,9 @@ added that can handle its combination of tags.
50
51
Before releasing the template version with configurable workspace tags, ensure
51
52
that every tag set is associated with at least one healthy provisioner.
52
53
54
+ > [ !NOTE] It may be useful to run at least one provisioner with no additional
55
+ > tag restrictions that is able to take on any job.
56
+
53
57
### Parameters types
54
58
55
59
Provisioners require job tags to be defined in plain string format. When a
@@ -66,6 +70,14 @@ the workspace owner to change a provisioner group (due to different tags). In
66
70
most cases, ` coder_parameter ` s backing ` coder_workspace_tags ` should be marked
67
71
as immutable and set only once, during workspace creation.
68
72
73
+ ** We recommend only using the following as inputs for ` coder_workspace_tags ` :**
74
+
75
+ - Static values (e.g. ` "developers" ` ),
76
+ - Template variables (e.g. ` var.az ` ),
77
+ - Coder parameters (e.g. ` data.coder_parameter.runtime_selector.value ` ).
78
+
79
+ Passing template tags in from other data sources may have undesired effects!
80
+
69
81
### HCL syntax
70
82
71
83
When importing the template version with ` coder_workspace_tags ` , the Coder
0 commit comments