Skip to main content

Worker Pool Job Routing

When drift detection is enabled on a stack, you are forced to use your self-hosted worker pool.

Workaround
No
Problem
Status: ⬆️ Gathering votes2 comments

Log in to comment and vote

Comments2

  • Yellow Coral

    •

    Apr 27

    Currently running up against this as well. Having to lock stacks to private pool in order to get drift detection means the public worker pool is effectively useless. I can think of a few ways to resolve this:

    1. Allow a stack to subscribe to multiple pools, allow routing/prioritization to pool based on workload. (e.g. proposed runs/tracked runs to public, drift detection to private)
    2. Remove the stack worker pool subscription config entirely, and allow pool selection at run-time via parameter.

  • Gold Patch

    •

    Jan 30

    The feedback form seems to have cut off the submission.

    You don’t always need to use your private worker to successfully conduct your normal Terraform operations (Tracked run plan/apply).

    Our team needs to be allowed to make use of all of our workers, both public and private, without locking all runs to a certain pool.

    An ideal scenario looks like this:

    • Drift detection runs route to the private worker

    • All other runs route to any worker (both public and private workers can pick up pending runs)