Automated Pulumi Stack Drift Detection
Every morning, WebRun opens Pulumi, checks every stack for drift between what the code declares and what's actually running, logs each drifted resource to Google Sheets with the stack and the difference found, and updates a Notion infra health page so a resource someone changed by hand outside Pulumi never quietly stays out of sync.
How do I catch infrastructure drift in my Pulumi stacks?
WebRun checks every Pulumi stack every morning for drift between code and live infrastructure. It logs each drifted resource to Google Sheets with the difference found, and updates a Notion infra health page, so a resource changed by hand outside Pulumi gets noticed instead of quietly staying out of sync. It never runs an update itself.
- Manual changes outside Pulumi get caught the next morning
- Every drifted resource is logged until it's reconciled
- Infra health is visible on one page instead of checked stack by stack
Built for infrastructure teams · platform engineers · DevOps · SRE teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.pulumi.comin a real browser with your saved login - no setup, no API keys. -
1
Pulumi - check stacks for drift
- Open Pulumi and run a preview on each stack to check for drift
- Capture the resource and the difference between code and live state for anything drifted
- Skip resources already logged as drifted this run
Done when Every drifted resource across all stacks is listed with its difference.
-
2
Notion - log every drifted resource
notion.so
WebRun opens Notion to log every drifted resource. - Log each drifted resource as a new row with its stack and difference
- Update the status of any resource already fixed since last check
- Keep the sheet as the record of open drift issues
Done when The sheet lists every currently drifted resource.
-
3
Google Sheets - update the infra health page
google.com
WebRun opens Google Sheets to update the infra health page. - Update the infra health page with the current drift count per stack
- List the most significant drifted resources
- Keep the page as the current source of truth for infra health
Done when The Notion page reflects every stack's current drift status.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it run an update to fix the drift?
No. WebRun only previews and reports drift. Running an update to reconcile infrastructure is always a deliberate action your team takes in Pulumi.
What counts as drift?
Any live resource that no longer matches what your Pulumi code declares, whether from a manual change or an external process.
How fast does new drift get noticed?
The morning after it happens, since every stack is previewed each day.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.