Skip to main content

Stacks with rejected runs should not become failed

Feature RequestsStacks

When a plan gets rejected in a stack the Stack goes to the Failed state. Is this really correct? In my mental model a failed stack would be one that if you run it it fails with an error. Setting a stack it Failed because the last plan was rejected seems to give incorrect signals about the state of the stack.

I even think that among the existing states, Discarded would make more sense than Failed (though I don't fully like that either)

Does this make sense from the point of view of Spacelift?

Workaround
No
Problem
Status: 🗑️ Archived3 comments

Log in to comment and vote

Comments3

  • Black Breeze

    •

    Feb 11

    The idea here is that behind each stack there’s a backing code that’s meant to be the golden representation of your infrastructure. When you reject a run, you’re saying something like “the current code does not represent my desired reality”. In my mind it’s a serious mismatch that is an alert-worthy condition.

    Does that explain my point of view?