getSignoffs

getSignoffs is the second step of a package deploy. It decides who must approve the deploy before it may change anything.

It takes the resources that getAffected found would be updated and collects their owners. Each owner becomes a required signer: nobody can overwrite a resource someone owns without that person’s approval.

Configuration

Updates

Updates is the list of resources the deploy would update, as returned by getAffected.

Return Values

Required Signers lists the users who must approve the deploy. Each owner appears once, however many of their resources are affected.

Runtime behavior

getSignoffs runs automatically and changes nothing in the workspace.

• When at least one affected resource has an owner, the step takes its success path, Sign-off required from the affected-resource owners. The deploy waits at absolute for those owners.
• When no affected resource has an owner, the step takes its failure path, No sign-off required (create-only) - deploy directly. This is not an error: the deploy skips the sign-off and goes straight to deploy.

Only an owner that was explicitly assigned counts. A resource without an owner needs no sign-off, and none is assumed.

Best practices

Assign an owner to the processes, datastores and integrations that matter. Then no package deploy can change them without that person’s approval.

Works well with

• getAffected, which supplies Updates.
• absolute, the sign-off the required signers receive.
• Process Owner, the owner who signs off.