It would be highly beneficial to configure stack behavior settings—such as auto-apply, auto-retry, and others—at scale, rather than having to set them individually for each stack.
For us, it’d be tremendously helpful to be able to set stack level settings on a Space level, and all of those stack inherits from that Space config.
We group stacks with Spaces already, and most of them have similar configs, for example, the “Prod” Space will always have Autodeploy to off.
Right now, we are configuring that with Terraform. But if set at the Space level, I think that is cleaner.
Black Breeze
•
Sep 11, 2025
Interesting…
Would the idea be to define them on space level and have them inherited like context or policy auto-attachments? Or would it be a global thing to enforce certain settings on every stack in an account? Or else, would you want to have like a collection of predefined presets that could be used to define multiple settings at the same time (like IDK, CSS classes?).
What would fit your use case best?
Purple Fries
•
Oct 1, 2025
A space-level definition with inheritance and auto-attachment would technically work, but I was thinking more along the lines of a UI-based solution. Ideally, it would allow users to select multiple stacks—using Views or labels—and then bulk edit settings like runner image, toggle autodeploy, autoretry, etc...
This approach would be especially useful for us since we manage a large number of stacks and rely heavily on Views and labeling.
Log in to comment and vote
Comments3
Yellow Coral
Jan 14
For us, it’d be tremendously helpful to be able to set stack level settings on a Space level, and all of those stack inherits from that Space config.
We group stacks with Spaces already, and most of them have similar configs, for example, the “Prod” Space will always have Autodeploy to off.
Right now, we are configuring that with Terraform. But if set at the Space level, I think that is cleaner.
Black Breeze
Sep 11, 2025
Interesting…
Would the idea be to define them on space level and have them inherited like context or policy auto-attachments? Or would it be a global thing to enforce certain settings on every stack in an account? Or else, would you want to have like a collection of predefined presets that could be used to define multiple settings at the same time (like IDK, CSS classes?).
What would fit your use case best?
Purple Fries
Oct 1, 2025
A space-level definition with inheritance and auto-attachment would technically work, but I was thinking more along the lines of a UI-based solution. Ideally, it would allow users to select multiple stacks—using Views or labels—and then bulk edit settings like runner image, toggle autodeploy, autoretry, etc...
This approach would be especially useful for us since we manage a large number of stacks and rely heavily on Views and labeling.