Drift alerts via Slack
Create a separate workflow file for drift
To run digger in drift detection mode, passmode: drift-detection
in the workflow file and configure the relevant crontab to run it with the frequency you want:
To limit drift checks to only certain projects/environments, use a dedicated Digger config file and point the workflow to it via
digger-filename
. See: Limit Drift Detection to Specific Projects.Configure Slack notification URL
Note theDRIFT_DETECTION_SLACK_NOTIFICATION
env var that the workflow above is using. This should be set to a Slack Incoming Webhook URL.
Follow the official Slack guide to get the Incoming Webhook URL; then add it as an Action secret named DRIFT_DETECTION_SLACK_NOTIFICATION
Drift alerts via Github Issues
Coming soon to CE, here is an example of how to configure it: https://github.com/diggerhq/demo-ee-features/edit/main/.github/workflows/drift.yml. Digger supports drift detection and automatic creation of issues in your ticketing system, e.g. GitHub Issues:
Troubleshooting
403 errors
If you are seeing permission errors such as 403 in the action log while reporting drift status the backend that is almost always due to missingno-backend: true
as an argument in the workflow file