Topic lessonTopic: Applied GitHub Actions and SQL Server recovery labs
Review Terraform plans and state before a GitHub Actions release
Distinguish proposed updates and replacements from current state bindings. Sensitive attributes can be retained in plans and state even when hidden in terminal output.
Hold a release for review when replacement affects a synthetic SQL Server data store.
The cases use fictional inputs.
What to predict
Distinguish proposed updates and replacements from current state bindings. Sensitive attributes can be retained in plans and state even when hidden in terminal output.
- Planned action → Data-retaining resourceAlign conditions
- Data-retaining resource → ReviewedCompare outcomes
- Reviewed → DecisionVerify the decision
- Planned action
- Update / Replace
- Data-retaining resource
- Yes / No
- Reviewed
- Yes / No
- Decision
- Hold a release for review when replacement affects a synthetic SQL Server data store.
Compare the cases
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | Planned action Update, Data-retaining resource Yes, Reviewed Yes | Review criteria met. The plan was reviewed; execution needs separate evidence. |
| Trial 2 | Planned action Replace, Data-retaining resource Yes, Reviewed Yes | Hold: a data-retaining resource would be replaced. Review protection and restoration. |
| Trial 3 | Planned action Update, Data-retaining resource Yes, Reviewed No | Hold: associate the inspected plan with an approval record. |
| Trial 4 | Planned action Replace, Data-retaining resource No, Reviewed Yes | Review criteria met. The plan was reviewed; execution needs separate evidence. |
Acceptance and limits
This models a synthetic action and review gate. It does not import or execute Terraform plans, state or configuration.
Read the initial conditions and operational goal.
Change one condition and compare the decision.
Record the model boundary and outstanding checks.
Change a condition
This models a synthetic action and review gate. It does not import or execute Terraform plans, state or configuration.
Review criteria met. The plan was reviewed; execution needs separate evidence.
{"replace":"Hold: a data-retaining resource would be replaced. Review protection and restoration.","review":"Hold: associate the inspected plan with an approval record.","ready":"Review criteria met. The plan was reviewed; execution needs separate evidence."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- Record the model boundary and outstanding checks.
Check your understanding: Hold a release for review when replacement affects a synthetic SQL Server data store.
This models a synthetic action and review gate. It does not import or execute Terraform plans, state or configuration.
Record the model boundary and outstanding checks.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsDistinguish proposed updates and replacements from current state bindings. Sensitive attributes can be retained in plans and state even when hidden in terminal output.
Used in this lessonWhat to predict Acceptance and limits