Match infrastructure back to its written configuration
Infrastructure changed by hand and never recorded in code, brought back in line, with the plan reviewed first.
The ticket
Reconcile one infrastructure stack with its declared configuration.
Acceptance criteria
- A plan showing the drift is attached
- Each drifted resource is either adopted into code or reverted, with a reason
- The apply stays with a person; this ticket delivers the plan
- Drift detection runs on a schedule afterwards
What lands as proof
Plan output enumerating every drifted resource, reviewed before anything is applied.
Why teams defer it
- The manual change fixed something urgent, and writing it back was never as urgent.
- Applying a plan against drifted infrastructure can destroy the fix somebody made by hand, so it needs reading carefully.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: reconcile one infrastructure stack with its declared configuration. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means plan output attached, the apply stays with the team, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.