- Customers that span AWS, Azure, GCP etc.
- Customers that need specific configurations like BYO-VPC vs fully managed BYOC
acme-aws and acme-azure. Keep each app in its own directory, and give
each one its own app branch that points at that directory. Each branch rolls changes out to its
installs in install groups:
Connecting each app to git
Each app ships through an app branch:-
Add a branch file, such as
branches/main.toml, that points at your repository, the app’s directory, and a git branch. -
Sync it once. After the first sync, the branch starts its first run.
- Push to that git branch to ship each change after that.
Splitting an app branch into install groups
Most teams don’t ship a change to every customer at once. A common rollout:- Canary: your internal and test installs get the change first.
- Customers: once the canary looks healthy, the change rolls out to customer installs, often in tiers.
order, and each one waits
for your approval unless it auto-approves when policies pass.
branches/main.toml (excerpt)
Default labels
Install groups pick installs by label. Default labels put a label on every install, so each new install joins the right group on its own. Set the value from an install input with templating:metadata.toml
- Change default labels in
metadata.toml. You can’t edit them on a single install. - The next app branch run updates every install.
Label colors
Color-code labels in the dashboard by label key:metadata.toml
Telling apps apart in the dashboard
Give each app a name and description inmetadata.toml. Nuon shows them in the dashboard and CLI:
metadata.toml
readme points to a Markdown file shown on each install. See Using READMEs.