What is an operation role
Roles that you can scope to the specific task, and use in runbooks so they have built in guardrails for your maintenance or upgrade activities.Required roles
Every app config must define three standard roles in its permissions config:- Provision: provisions and reprovisions the install, and deploys all components.
- Deprovision: deprovisions the install, and tears down all components.
- Maintenance: everything else, such as single component deploys, action runs, and input changes.
Scope custom operation roles to a task
Add more specific roles matching how you manage your customer environments, for example:- Deploy and teardown for one component: a deploy role that can create and update the component’s Lambda function, and a teardown role that can only delete it. See the deploy and teardown example.
- An action that rotates a password: a role that can only update that one secret, set on the action. See assign a role to an entity.
- One role for every teardown: an app-wide rule that sends all component teardowns to a delete-only role. See set app-wide rules.
When Nuon uses a role
Each time Nuon changes something in your customer’s account, the runner assumes a role to do it. That happens when it:- Sets up, updates, or removes the install’s base infrastructure (the sandbox)
- Deploys or removes a component
- Runs an action
- On the sandbox, a component, or an action: in its config file.
- For the whole app: with rules in
operation_roles.toml, such as one role for every component teardown. - For a single run: from the dashboard or command line.
Next steps
- Operation Roles guide: define roles, assign them, and override them for a run
- Break Glass: elevated access your customer switches on when you need it
- Permissions config reference: every field in
permissions.toml