DEVOPS
Agent-Driven Drift Triage with Reconciliation Proposal
An agent investigates each detected Terraform drift, decides whether to import, revert, or update code, drafts a reconciliation PR, and asks the owning team to approve in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled drift sweep
- Actionterraform plan, collect drifted resourcesShell
- ActionGather GitHub + Datadog context per resourceGitHub
- LogicAgent classifies: import / revert / codify
- ActionOpen draft reconciliation PRGitHub
- OutputPost proposal to Slack for approvalSlack
What it does
For each drifted resource, an agent reads the plan diff, recent GitHub history, and Datadog change context to reason about why the resource drifted, then recommends one of three resolutions: import the live change into state, revert it via apply, or update the Terraform code to match. It drafts the corresponding GitHub PR and requests human approval in Slack.
When to use it
Use it when raw drift alerts aren't actionable enough and you want a first-pass judgment — distinguishing an intentional hotfix that should be codified from an accidental change that should be reverted — before a human commits time to it.
How it works
- 1A scheduled trigger kicks off a drift sweep.
- 2An action runs `terraform plan` and collects each drifted resource.
- 3The agent gathers context from GitHub commit history and Datadog change events per resource.
- 4A logic step has the agent classify each drift as import, revert, or codify.
- 5An action opens a draft GitHub PR with the proposed reconciliation.
- 6An output step posts the recommendation and PR link to Slack for owner approval.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.