@johnstcn I would like to propose a different design. What do you think about having the provisioner tags as a section in the form? Also, is this only required on creating a starter template or any template at all?

@johnstcn I would like to propose a different design. What do you think about having the provisioner tags as a section in the form?

That's fine too! As long as there's an equivalent place to set provisioner tags as with the CLI --provisioner-tag flag.

Also, is this only required on creating a starter template or any template at all?

For consistency we could show it on any templates. I don't see any reason that we shouldn't show it on templates imported from elsewhere (e.g. uploaded).

@f0ssel @bcpeinhardt we need to consider this while working on importing registry templates.

@BrunoQuaresma your proposal looks good to me and it serves the purpose.

I'm almost done. I just need to add some tests to finish it, but before doing that, I want to confirm the behavior on the quick demo that I recorded below:

@BrunoQuaresma WDYT, the Provisioners tags section will only be visible if external provisioners are configured. For internal ones, we generally do not use tags (technically, we can, I think).

The suggestion is to make the UI less confusing for users who do not use external providers with special tags and keep the current behavior.

@johnstcn and @spikecurtis may provide more context here.

@matifali I didn't understand your point or what changes should be made 😕

@matifali makes a good point. If there are no external provisioners in a deployment, there is no need to show this extra stage. If it is shown unnecessarily, users may erroneously enter provisioner tags that are not needed and be faced with a stuck workspace build.