← Back to all posts

Stacks should match on most relevant name

If a there are two stacks that have matching prefixes, both stacks are triggered. We expect the stack that best matches the prefix should trigger a run.

Workaround
Create a push policy that only looks at the specified directory and ignores nested directories.
Problem
Setup: The following stacks have corresponding root directories: * resources/a * resources/a/b If a change is only made in b, both stacks are triggered. We expect that the stack only runs in resources/a/b. The problem with the workaround of the push policy is that there may be stacks that are configured to run for multiple subdirectories. This should continue to be supported. Using the above push policy, we're forced to create a stack for every folder where we plan to have terraform state.

Please authenticate to join the conversation.

Upvoters
Status

👀 In Review

Board

💡 Feature Requests

Tags

Stacks

Date

6 months ago

Subscribe to post

Get notified by email when there are changes.