INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Hold a release for review when replacement affects a synthetic SQL Server data store.

Prerequisite

The cases use fictional inputs.

Start the exercise →

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.

From conditions to the decision
From conditions to the decision1: Planned action — Align conditions — Data-retaining resource. 2: Data-retaining resource — Compare outcomes — Reviewed. 3: Reviewed — Verify the decision — Decision123Planned actionData-retainingresourceReviewedDecisionFrom conditions to the decision1: Planned action — Align conditions — Data-retaining resource. 2: Data-retaining resource — Compare outcomes — Reviewed. 3: Reviewed — Verify the decision — Decision123Planned actionData-retainingresourceReviewedDecision
  1. Planned action → Data-retaining resourceAlign conditions
  2. Data-retaining resource → ReviewedCompare outcomes
  3. 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

Synthetic observations
CaseConditionsDecision
Trial 1Planned action Update, Data-retaining resource Yes, Reviewed YesReview criteria met. The plan was reviewed; execution needs separate evidence.
Trial 2Planned action Replace, Data-retaining resource Yes, Reviewed YesHold: a data-retaining resource would be replaced. Review protection and restoration.
Trial 3Planned action Update, Data-retaining resource Yes, Reviewed NoHold: associate the inspected plan with an approval record.
Trial 4Planned action Replace, Data-retaining resource No, Reviewed YesReview 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.

Check your understanding

Choose an option to see the result and explanation.

What happens in trial 1?
Read the answer and reason

Answer: Review criteria met. The plan was reviewed; execution needs separate evidence. · Planned action Update, Data-retaining resource Yes, Reviewed Yes → Review criteria met. The plan was reviewed; execution needs separate evidence.

What happens in trial 2?
Read the answer and reason

Answer: Hold: a data-retaining resource would be replaced. Review protection and restoration. · Planned action Replace, Data-retaining resource Yes, Reviewed Yes → Hold: a data-retaining resource would be replaced. Review protection and restoration.

What happens in trial 3?
Read the answer and reason

Answer: Hold: associate the inspected plan with an approval record. · Planned action Update, Data-retaining resource Yes, Reviewed No → Hold: associate the inspected plan with an approval record.

Check, then explain in your own words

  1. Read the initial conditions and operational goal.
  2. Change one condition and compare the decision.
  3. 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.