← Back to all posts

Stack Dependencies - allow dependent stack to be triggered when it would have been "affected"

Currently with stack dependencies that share outputs, if the output hasnt changed but the dependent stack is affected by the push - the run will still be skipped as the output has not changed.

Workaround
Always trigger button. A trigger policy that triggers the stack.
Problem
- Problem with always trigger button is it can cause unnecessary runs. - The trigger policy workaround is not an elegant solution - Without either of the above, the stack has skipped runs when it was expected it would have been triggered. Given two stacks: A and B, where B depends on output A.a, we get the following issue: If both A and B are based on the same source repository and there is a PR commit that affects both of them, but does not change the output A.a, then the Run for B gets skipped in spite of the code changes that affect it.

Please authenticate to join the conversation.

Upvoters
Status

⬆️ Gathering votes

Board

💡 Feature Requests

Tags

Stack Dependencies

Date

About 1 year ago

Subscribe to post

Get notified by email when there are changes.