@@ -165,20 +165,10 @@ inside the Terraform. See the
165
165
[workspace tags documentation](../admin/templates/extending-templates/workspace-tags.md)
166
166
for more information.
167
167
168
- <<< <<< < HEAD
169
168
> [! NOTE]
170
169
> Workspace tags defined with the ` coder_workspace_tags` data source
171
170
> template ** do not** automatically apply to the template import job! You may
172
171
> need to specify the desired tags when importing the template.
173
- =======
174
- < blockquote class=" admonition note" >
175
-
176
- Workspace tags defined with the ` coder_workspace_tags` data source template
177
- ** do not** automatically apply to the template import job! You may need to
178
- specify the desired tags when importing the template.
179
-
180
- < /blockquote>
181
- >>>>>>> c7a48ec08 (replace [! NOTE])
182
172
183
173
A provisioner can run a given build job if one of the below is true:
184
174
@@ -200,7 +190,6 @@ However, it will not pick up any build jobs that do not have either of the
200
190
from templates with the tag ` scope=user` set, or build jobs from templates in
201
191
different organizations.
202
192
203
- <<< <<< < HEAD
204
193
> [! NOTE]
205
194
> If you only run tagged provisioners, you will need to specify a set of
206
195
> tags that matches at least one provisioner for _all_ template import jobs and
@@ -209,19 +198,6 @@ different organizations.
209
198
> You may wish to run at least one additional provisioner with no additional
210
199
> tags so that provisioner jobs with no additional tags defined will be picked
211
200
> up instead of potentially remaining in the Pending state indefinitely.
212
- =======
213
- < blockquote class=" admonition note" >
214
-
215
- If you only run tagged provisioners, you will need to specify a set of tags
216
- that matches at least one provisioner for _all_ template import jobs and
217
- workspace build jobs.
218
-
219
- You may wish to run at least one additional provisioner with no additional tags
220
- so that provisioner jobs with no additional tags defined will be picked up
221
- instead of potentially remaining in the Pending state indefinitely.
222
-
223
- < /blockquote>
224
- >>>>>>> c7a48ec08 (replace [! NOTE])
225
201
226
202
This is illustrated in the below table:
227
203
@@ -401,16 +377,6 @@ This can be disabled with a server-wide
401
377
coder server --provisioner-daemons=0
402
378
` ` `
403
379
404
- # # Manage external provisioners
405
-
406
- You can view more information about and manage your provisioners from the Coder
407
- dashboard.
408
-
409
- Under ** Admin settings** select **Organizations**, then select **Provisioners**.
410
-
411
- Use the ** Jobs** or ** Daemons** tab to view provisioners and their status, and
412
- delete provisioners as necessary.
413
-
414
380
# # Prometheus metrics
415
381
416
382
Coder provisioner daemon exports metrics via the HTTP endpoint, which can be
0 commit comments