Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Interpret template readiness and upgrade risk before clicking apply.

​
Prerequisites

  • A template-backed stack or template detail view

​
Workflow

1
Read the current status: up to date, update available, blocked, or unknown.
2
Review risk level, blocking reasons, and service notes.
3
Use high-risk previews as operator decisions, not casual updates.

​
What can block an update

  • Missing required inputs for the newer template version
  • Template drift between the live stack and recorded template provenance
  • High-risk changes to service identity or persistent-volume expectations

​
Reading risk and service notes

An upgrade is not just available or unavailable — it carries a risk level and the template’s own service notes. Service notes are where a template author flags things like data migrations, breaking changes, or volume implications. Read them before applying; a low-risk patch and a high-risk version bump deserve different care.

​
Treat high-risk upgrades as decisions

  • Back up stateful stacks before a high-risk upgrade.
  • Preview the diff and resolve any missing inputs first.
  • Remember an upgrade can be rolled back, but a corrupted data migration may not be — that is why the backup comes first.

​
Expected result

Template lifecycle decisions feel deliberate instead of surprising.

Updating template-backed stacks

Preview diffs, resolve missing inputs, and apply the latest published template version safely.

Template inputs and secrets

Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.

Back up and restore a stack

Use S3-backed named-volume archives to protect and recover stateful stack data.