Digger EE supports drift detection and automatic creation of issues in your ticketing system, e.g. GitHub Issues:
Digger CE only supports drift alert via Slack. It was previously documented under CE; you can still use the basic Slack alerts for free.
Limitations of drift detection in CE:
To configure basic drift alerts via Slack:
To run digger in drift detection mode, pass mode: drift-detection
in the workflow file and configure the relevant crontab to run it with the frequency you want:
Note the DRIFT_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
For using drift detection with gitlab, a similar workflow can be used:
The above workflow will detect drift for the repository projects and post if any instances of drift occur to slack
Digger EE supports drift detection and automatic creation of issues in your ticketing system, e.g. GitHub Issues:
Digger CE only supports drift alert via Slack. It was previously documented under CE; you can still use the basic Slack alerts for free.
Limitations of drift detection in CE:
To configure basic drift alerts via Slack:
To run digger in drift detection mode, pass mode: drift-detection
in the workflow file and configure the relevant crontab to run it with the frequency you want:
Note the DRIFT_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
For using drift detection with gitlab, a similar workflow can be used:
The above workflow will detect drift for the repository projects and post if any instances of drift occur to slack