Goal
Avoid misconfiguring a service by treating template inputs as throwaway form fields.Prerequisites
- A template detail page or deploy flow
Workflow
Required vs optional inputs
The template detail page shows how many inputs a template needs and how many are secret. Required inputs must be supplied before the template can render into a stack; optional inputs fall back to the template defaults.Secrets are handled differently
- Secret inputs (passwords, API keys, tokens) are treated as sensitive rather than plain defaults.
- Provide real values at deploy rather than leaving placeholders in a secret field.
Inputs and upgrades
Saved inputs are reused when you upgrade a template-backed stack to a newer version, so you do not re-enter everything. When a newer version introduces a new required input, the upgrade preview flags it as missing so you supply it before applying.Expected result
Template deployment inputs are supplied deliberately and with less surprise at upgrade time.
Related guides
Deploy from a template
Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.
Updating template-backed stacks
Preview diffs, resolve missing inputs, and apply the latest published template version safely.
Template upgrade safety and service notes
Understand why an upgrade is safe, risky, or blocked, and how template readiness notes should influence operator decisions.