Skip to main content
Once a customer’s install is running, they’ll still need to make a few changes themselves, such as fixing a setting, approving an update, or removing your product from their account. This guide covers the API calls behind those controls in your app. For first-time setup, see Build a UI integration. Every call here uses your app’s service account token. Calls that start work accept a request_id, so a retry after a timeout returns the original workflow. See Idempotent operations.

Change a setting

When a customer fixes a setting, such as their domain, update the install’s inputs. Nuon redeploys the parts of your product that use them.

Pick up a changed secret

Customers keep secrets in their own cloud’s secret manager. After they change one, sync it so your product uses the new value.

Approve changes

New versions of your product, and any other change that waits for approval, reach the customer one step at a time. Find the waiting steps:
Then send the customer’s approval:
To choose which steps wait for the customer, see Getting customer approvals.

Remove your product

Removing an install runs setup in reverse:
  1. Deprovision your product from the customer’s account.
  2. The customer removes the runner, following the steps in the deprovision workflow.
  3. Delete the install from Nuon.

Deprovision

Deprovisioning removes your product and its base infrastructure from the customer’s account. Like setup, it can pause for approval.

Delete the install

Once everything is gone from the customer’s account, delete the install.

Forget an install

If something outside Nuon breaks the customer’s account badly enough that deprovisioning can’t run, forget the install instead. Nuon drops its record without touching the account, and you can start a fresh install.