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