Distributed Lock Patterns

Within a stack dependency chain we have stages per environment, separated by external dependencies (UAT & Validation frameworks) that ensure the infra changes are working as expected.

Multiple Stacks within the dependency chain align with an environment. As a basic example, Stacks 1-8 are assigned to Test, 9-21 are Pre Prod and 22-35 are Production.

Current Spacelift behavior is to queue new runs while another run is active for the same stack, which causes problems when we are updating subsequent stacks within the chain for that same environment (prior to validation).

Obviously we do not want new changes going in that effect validation runs. Right now we handle that with a manual trigger for the chain but this is far from ideal.

The feature request would be to group stacks within the chain into ‘environment’ blocks where the queue only triggers the next run after the block is complete (including the external dependencies) and remove the need for manual triggers.