The stack_activator resource can be used to disable a stack. This is helpful if I’m inferring the creation of many stacks from an input config to an admin stack, but some subset of those need to be disabled. If a new stack is disabled it stays in the None state, but if a stack is in another state and is then disabled, its state stays that way. If the stack was in an undesirable state like Discarded or Failed, that stack will show up elsewhere when trying to surface stacks in a bad state. It would be great if:
The stack activator resource could set the stack state
OR, it put the stack in a new Disabled state
I’m considering this to be an important feature. A primary benefit to using Spacelift is the automation it provides around “vanilla” terraform workflows. Some of this automation would greatly benefit from the above feature.
Please authenticate to join the conversation.
🔭 Discovery
💡 Feature Requests
5 months ago
Get notified by email when there are changes.
🔭 Discovery
💡 Feature Requests
5 months ago
Get notified by email when there are changes.