main.tf rules, the template.json schema, the variable types Amnify understands, and two complete worked examples (Azure Resource Group and AWS VPC).
What a Template Is, Concretely
A template is a directory in your GitHub repository that contains:- One or more
.tffiles — the Terraform definition of the infrastructure. - One
template.jsonfile — a manifest that tells Amnify how to render the input form, validate user input, store secrets, and wire up cloud-resource pickers.
template.json; it executes terraform against your .tf files. The two files are paired, and variable names must line up between them.
How Templates Flow Into Amnify
The sync is manual — Amnify does not auto-pull from GitHub. After pushing, click Sync Templates in the Amnify UI to make new or updated templates available.Prerequisites
Before authoring your first template, make sure:- Your organization has a synced GitHub template repository. See Integrations → GitHub for the connection setup.
- You have write access to that repository (or can open a pull request against it).
- You are comfortable writing Terraform for the resources you intend to provision.
- Your local machine has the
terraformCLI installed for offline validation (recommended).
How to Read This Section
Related Reading
- Using Templates — the consumer view: browsing, selecting, and modifying templates from the library.
- Templates concept page — high-level mental model.