Skip to main content

Support for exclusion patterns in additional_project_paths or Project globs (e.g., !path/to/exclude/*).

Feature Requests

We would like to have support for exclusion patterns in additional_project_paths or Project globs (e.g., !path/to/exclude/*).
We have several cases of stacks that should trigger on changes to all subdirectories (for example, the stack envs/prod should watch envs/prod/**/*.tf) except for a specific directory envs/prod/grafana, which has its own dedicated stack. Without exclusion support, we need to explicitly list every subdirectory we want to monitor. This is really difficult to maintain as subdirectories are added.Our proposed solution is to allow glob negation patterns like additional_project_paths = ["envs/prod/**/*.tf", "!envs/prod/grafana/**"] to explicitly exclude paths from triggering the stack. This would mirror the behavior of commonly used tools like .gitignore

Status: ❌ Rejected1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    Nov 25, 2025

    Thanks for the detailed feature request! I understand the maintenance challenge you're facing with having to explicitly list every subdirectory.

    The good news is that this functionality is already available today using Push Policies, which are actually the right tool for this type of complex path-based logic.

    If you need assistance creating the exact policy that will fit your use case, please reach out to your friendly Spacelift Solutions Engineer and they’ll be able to help.