Normalize infrastructure resource actions for review
Review summaries collapse updates and replacements into one change count.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Infrastructure analysis
Estimated field mix
- Cloud infrastructure70%
- Developer tooling30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional application team manages a small database, cache, and object store. Reviewers struggle to distinguish harmless configuration changes from destructive replacements.
Setup prerequisites
- Author synthetic infrastructure plans and state snapshots; use local files only and no cloud credentials.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Separate create, update, replace, and delete actions.
- Preserve resource addresses and dependencies.
- Represent unknown values explicitly.
Implementation constraints
- Treat plan JSON as untrusted data.
Verification to include
- Parse a valid mixed-action plan.
- Reject malformed action combinations.
Deliverables
- Plan action model.
Rollout and recovery
Adopt read-only summaries before any execution integration.
Value of the work
For the engineer: Practice infrastructure risk analysis, plan integrity, and least-privilege change workflows.
For the team: Give infrastructure reviewers concrete change scope and recovery consequences.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.