Skip to content

Provisionerd should register the running provisioners when it connects #1605

Closed as not planned

Description

@spikecurtis

What is your suggestion?

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?

Always start all provisioners.

Are you interested in submitting a PR for this?

yes

Activity

  1. 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
  2. reopened this on Jul 28, 2022
  3. kylecarbs commented on Aug 24, 2022

    @kylecarbs
    Member

    @dwahler this might be smart to include as part of #3563 . Thoughts?

  4. self-assigned this
    on Aug 30, 2022
  5. bpmct commented on Oct 25, 2022

    @bpmct
    Member

    going to close as part of #44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

apiArea: HTTP API

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions