Skip to main content

Default worker pool at space or organization level

Feature RequestsWorkers

It would be helpful to set a private workerpool as the default for all stacks organization-wide.

Workaround
Problem
Status: ⬆️ Gathering votes7 comments

Log in to comment and vote

Comments7

  • Jonah Kowall

    Team•

    Jul 14

    Thanks for the well-written request, and for being explicit that the goal is a break-glass process rather than a day-to-day workflow.

    After discussion we've decided not to build this, so I'm closing it out. The reason is that exposing the managed state backend for direct local plan and apply would bypass the Spacelift control plane entirely.

    A local run against our backend produces no run in Spacelift: no plan or approval policy evaluation, no run history, and no audit trail of what changed or who changed it. Locking alone doesn't preserve those guarantees, and for most of our customers those guarantees are the reason Spacelift manages state in the first place.

    We recognize emergencies happen and today's answer (manual state surgery and reconciliation) is painful. If you hit a situation where you need to operate on state outside a normal run, please open a support ticket and we'll help you through it safely.

    • Azure Chipmunk

      •

      Jul 14

      I think you may have replied to (and closed out) the wrong post. This is for having an org-wide default worker pool.

      • Lavender Walrus

        •

        Jul 27

        I agree. The comment by @Jonah Kowall appears unrelated to this feature request, which remains a critical need for us, so that we can manage customized runner pool images for our worker pools centrally.

        • Jonah Kowall

          Team•

          Jul 27

          Sorry about that gents, let me re-open.

  • Emerald Milkyway

    •

    Jun 4

    Being able to set the default workers at a space level would also be useful for us. right now we manage thousands of stacks, and making a runner change involves many applies to reconfigure. While automated, it’s still a painful process to reconfigure a default setting.

  • Black Breeze

    •

    Mar 17

    Hey @Bryan Banks !

    Thanks for submitting the feature request. While I appreciate that one of our competitors have this feature, at Spacelift we’re less about feature parity and more about solution completeness.

    If that’s OK, I’d like to dig a bit deeper into a few things.

    First, you’ve mentioned that you don’t manage stack creation via Terraform code. Is this by design, or is it an interim migration phase and that’s the end goal? If not - why not?

    What is driving the need for the default pinning? Is it security? Are you afraid that a new stack may use an incorrect worker pool? Or is it more a convenience thing, where you’d like to have the worker pool dropdown pre-populated by what’s considered a default for a given space/account? (currently the default is the public worker pool which is available to everyone).

    Thanks in advance for your patience!

  • Black Stream

    •

    Mar 13

    I am open to how the solution is implemented. In TFC, there is simply an org-wide “default execution mode” where you select the worker pool you want to default to. If Spacelift used a Context or Label driven design, that would be fine too.