Description
Background
The introduction of Organizations (Beta) revealed some bugs and nuanced behaviors with how provisioners, tags, and templates work. Today, there are many scenarios where a workspace or template job gets stuck in an infinite Pending state, because there is no corresponding provisioner with the necessary tags. However, it is challenging for a user or admin to understand why. There are also some bugs and edge cases in this flow that we need to fix around the provisioner experience.
Phase 0 (This week)
Improve our Helm charts and documentation on how to deploy provisioners and how tags work:
- chore(docs): fix inconsistencies in external provisioner docs #15416
- fix(helm/provisioner): prefer provisioner key if both psk and key are set #15417
Phase 1 (December 3 Release)
As an user, I need to understand why my workspace is stuck in a pending state and which tags are assigned to the job via clear UI warnings
As an admin, I want to use the same provisioners for template imports as workspace builds when I use the coder_workspace_tags data source in my templates
- Evaluate
coder_workspace_tagsduring template create/push #15427 - feature: extract
coder_workspace_tagsfrom template, detect dangerous data source usage #15087
As an admin, I want consistent and predictable behaviors when I use coder_workspace_tags data source, and want clear warnings when it is being used incorrectly
Phase 2 (January 7 Release)
As an admin, I want to import starter templates and either A) see provisioner tags or B) have a guarantee it'll be imported to a generic provisioner
As an admin, I want to be able to browse/delete/cancel provisioner jobs in the UI, especially ones that are stuck in pending