Policies
Policies
Articles
- Retrying failed drift detection runs
- Setting Up Notifications for Unconfirmed runs after x amount of time
- How do I restrict run promotion access to specific roles?
- Attaching a Policy to Multiple Stacks
- How to trigger Spacelift runs only for PR changes
- Troubleshooting notification policies that stopped triggering
- What are the possible values for the run action field in Notification Policies?
- Auto-deploying scheduled runs while requiring confirmation for manual runs
- How do I exclude specific stacks from auto-attached policies?
- When to use trigger policies vs dependencies
- Can I map GitHub usernames to Spacelift users in policies for GitOps workflows?
- Using Slack Channel IDs vs Names in Notification Policies
- How do notification policies work with spaces and stacks?
- Using a Scanning Tool in Spacelift (TFLint, TFScan, Checkov)
- How to Cancel In-Progress Runs with a New Commit
- How do I automatically confirm runs based on certain conditions?
- Setting Up Different Permissions for Users
- Using Multiple Policies of the Same Type
- How to trigger stack runs when a module version is updated
- Setting up Infracost plan policies with custom data input
- How to route Spacelift notifications between Slack and incident management tools
- Can I suppress VCS messages in Push policies for tracked commits?
- Targeting the Right Pull Request in Notification Policies
- Filtering Ansible drift detection notifications to exclude non-changes
- Can I disable or restrict the "Discard Run" action in Spacelift?
- Why can't I assign roles to API keys through the UI?
- How do I make a notification policy trigger only for stacks with specific labels?
- Drift Detection False Positives in Notification Policies
- Why can't I see policy input data in the simulation panel?
- Understanding pull_request_id in Notification Policy Data Input
- How to trigger pipeline runs only after PR merge (not on PR open/update)
- Canceling runs in different states with a push policy