Drift Detection — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— IaC Drift Detection
⏰Schedule
🔍Detect
📊Parse
🚨Alert
🔧Remediate
🎯 Next: Test →
Step 1 / 5
Speed
Scheduling
Cron trigger runs drift detection every night at 2 AM💡 Analogy
Scheduled drift detection is like a nightly audit — while everyone's asleep, the system checks if anything changed without authorization.
The GitHub Actions schedule trigger runs the drift workflow on a cron schedule. 2 AM UTC catches overnight manual changes before the engineering day starts.
Console Output
# GitHub Actions: Workflow triggered
# Event: schedule (cron: 0 2 * * *)
# Repository: org/infra-repo
# Branch: main

2024-07-15 02:00:00 UTC - Starting drift detection workflow...
Runner: ubuntu-latest (GitHub-hosted)
●.github/workflows/drift-detect.yml
SchedulingL1–10
1name: Drift Detection
2on:
3  schedule:
4    - cron: '0 2 * * *'  # 2 AM UTC nightly
5  workflow_dispatch:       # Manual trigger
6 
7permissions:
8  id-token: write          # For OIDC → Azure
9  contents: read
10  issues: write            # To create drift issues
11 
12jobs:
13  detect-drift:
14    runs-on: ubuntu-latest
15    steps:
16      - uses: actions/checkout@v4
17 
18      - name: Azure OIDC Login
19        uses: azure/login@v2
20        with:
21          client-id: ${{ secrets.AZURE_CLIENT_ID }}
22          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
23          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
24 
25      - name: Terraform Init
26        run: terraform init
27 
28      - name: Detect Drift
29        id: drift
30        run: |
31          terraform plan -refresh-only \
32            -out=drift.tfplan \
33            -detailed-exitcode
34          echo "exit_code=$?" >> $GITHUB_OUTPUT
35        continue-on-error: true
36 
37      - name: Parse Drift Severity
38        if: steps.drift.outputs.exit_code == '2'
39        run: |
40          terraform show -json drift.tfplan | \
41            jq '.resource_changes[] | select(.change.actions != ["no-op"])' \
42            > drift-report.json
43          python scripts/score_drift.py drift-report.json
44 
45      - name: Create GitHub Issue
46        if: steps.drift.outputs.exit_code == '2'
47        uses: actions/github-script@v7
48        with:
49          script: |
50            github.rest.issues.create({
51              owner: context.repo.owner,
52              repo: context.repo.repo,
53              title: '🚨 Infrastructure Drift Detected',
54              body: require('fs').readFileSync('drift-report.md', 'utf8')
55            })
55 lines
Timeline — 5 Steps
Scheduling
Cron trigger runs drift detection every night at 2 AM💡 Analogy
Scheduled drift detection is like a nightly audit — while everyone's asleep, the system checks if anything changed without authorization.
The GitHub Actions schedule trigger runs the drift workflow on a cron schedule. 2 AM UTC catches overnight manual changes before the engineering day starts.
Console Output
# GitHub Actions: Workflow triggered
# Event: schedule (cron: 0 2 * * *)
# Repository: org/infra-repo
# Branch: main

2024-07-15 02:00:00 UTC - Starting drift detection workflow...
Runner: ubuntu-latest (GitHub-hosted)

Was this page helpful?

Discussion

Cron trigger runs drift detection every night at 2 AM

💡 Analogy

Scheduled drift detection is like a nightly audit — while everyone's asleep, the system checks if anything changed without authorization.

The GitHub Actions schedule trigger runs the drift workflow on a cron schedule. 2 AM UTC catches overnight manual changes before the engineering day starts.

Console Output

# GitHub Actions: Workflow triggered
# Event: schedule (cron: 0 2 * * *)
# Repository: org/infra-repo
# Branch: main

2024-07-15 02:00:00 UTC - Starting drift detection workflow...
Runner: ubuntu-latest (GitHub-hosted)

Cron trigger runs drift detection every night at 2 AM

💡 Analogy

Scheduled drift detection is like a nightly audit — while everyone's asleep, the system checks if anything changed without authorization.

The GitHub Actions schedule trigger runs the drift workflow on a cron schedule. 2 AM UTC catches overnight manual changes before the engineering day starts.

Console Output

# GitHub Actions: Workflow triggered
# Event: schedule (cron: 0 2 * * *)
# Repository: org/infra-repo
# Branch: main

2024-07-15 02:00:00 UTC - Starting drift detection workflow...
Runner: ubuntu-latest (GitHub-hosted)