Make a staging environment match production again
A staging environment whose settings no longer match production, corrected so testing there is trustworthy.
The ticket
Close the configuration drift between a staging environment and production.
Acceptance criteria
- A configuration diff between the two is produced
- Each difference is closed or documented as deliberate
- Deliberate differences are recorded where the environments are documented
- No production credential or dataset is copied into the lower environment
What lands as proof
A configuration diff where every remaining difference is annotated as intentional.
Why teams defer it
- Staging works well enough to sign things off, which is exactly what makes the drift dangerous.
- Some differences are deliberate and undocumented, so closing them blindly breaks the environment.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: close the configuration drift between a staging environment and production. 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 a diff of the two configurations, with the drift closed, 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.