Using the CLI to create and manage installs
The CLI allows you to embed install management scripts, or install provisioning into your workflow.CLI Reference documentation can be found here.This page is specific to install management from the CLI.
--install-id/-i to target a specific install, or you can pin a default with nuon installs select and omit the flag on subsequent commands.
Create an install
Before creating an install, runnuon auth login to authenticate and nuon apps select to make sure you are on the right app.
--name— the name for this install--region— the cloud region to provision into--inputs—key=valuepairs for the app’s inputs
Find and select an install
List, fetch, and pin installs:-i.
Inspect and update inputs
Config-file-driven installs
You can describe installs declaratively in TOML files and sync them to Nuon. This is the pattern used in CI and for managing many installs at once.Deploy and redeploy components
Manage workflows and approvals
Install lifecycle events run as workflows. The CLI has an optional TUI that you can start with:
Reprovision, deprovision, forget
forget removes an install from the control plane without running deprovision workflows. Reserve it for installs that are stuck in an unrecoverable state.
Extend the CLI
The CLI is extensible — you can publish your ownnuon <tool> commands that ship alongside install management. For how to build, distribute, and auth custom commands, see the CLI Extensions guide.