Stacks with rejected runs should not become failed

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
Difficult to filter out really failed stacks vs stacks with rejected runs. This is specially prominent in our case because in oiur dev environments we don't want to run dependecy runs, so we reject them, and then all stacks become failed (see this feature request for context https://feedback.spacelift.io/p/do-not-trigger-runs-when-dependency-changes)

Please authenticate to join the conversation.

Upvoters
Status

πŸ”­ Discovery

Board

πŸ’‘ Feature Requests

Tags

Stacks

Date

About 13 hours ago

Subscribe to post

Get notified by email when there are changes.