You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provisionerd should register the running provisioners when it connects #1605
Right now we just hardcode the provisioner types that are registered to a provisionerd in the database, but you can start provisionerd with different sets. In our unit tests, we start only echo, in production we start only terraform. Instead of hardcoding, the provisionerd should send a registration message on connection that says which provisioners it is running.
Why do you want this feature?
This can help us detect config errors where templates are created for provisioner types that aren't supported by the cluster, and can prevent jobs from being sent to provisionerds that cannot run them.
Are there any workarounds to get this functionality today?
changed the title [-]Feat: provisionerd should register the running provisioners when it connects[/-][+]Provisionerd should register the running provisioners when it connects[/+]on Jun 7, 2022
Activity
[-]Feat: provisionerd should register the running provisioners when it connects[/-][+]Provisionerd should register the running provisioners when it connects[/+]kylecarbs commentedon Aug 24, 2022
@dwahler this might be smart to include as part of #3563 . Thoughts?
bpmct commentedon Oct 25, 2022
going to close as part of #44