Skip to main content

Allow runtime config to override worker pool for a run

Feature Requests

We have some directories where if we change a Terraform module they use, we need to retrigger plans on ~500 directories. However, in that case, we don’t want to clog up the queue for our normal worker pool. It would be nice if we could specify a different worker pool to use solely for the one triggered run from the module change.

Workaround
Status: 🗑️ Archived4 comments

Log in to comment and vote

Comments4

  • Black Breeze

    •

    May 8, 2025

    Thanks for the context. It sounds like the deeper goal is to avoid clogging the queue with bulk-triggered runs after module changes—especially when they’re lower priority than day-to-day work.

    Good news: Spacelift already supports run prioritization via policies. You can declare, for example, that runs triggered by changes only in specific paths (like shared modules) do not get a priority, so they don’t compete with critical workflows which are prioritized.

    This lets you deprioritize at the source, without needing to route through a separate worker pool.

    Quick question back: does this solve the core problem? Or is there a scenario where path-based priority wouldn’t capture the nuance?