deploy

deploy is the last step of a package deploy. It applies a package to your workspace.

It runs after the owners of the affected resources have approved in absolute, or straight after getSignoffs when nobody had to sign off.

Note

deploy is a platform step. metamorphOS runs it for you when you deploy a package from Resources. It is not meant to be added to your own processes.

Configuration

Package

Package is the package to deploy. When you deploy from Resources, metamorphOS fills it in.

The step returns no values. Its result is the change to your workspace.

Runtime behavior

deploy runs automatically.

Processes, datastores and integrations in the package are created when they are new to the workspace, and updated to a new revision when they already exist. Each keeps the identity it has in the package, so a later deploy of the same package updates the same resources.
Authorities, groups and organizations are created when they are missing. Ones that already exist are left as they are, and their members are not touched.
Files the package carries are copied into the workspace.
Integrations arrive without credentials. Credentials never travel in a package: connect the integration in the target workspace before you use it.

When everything is applied, the package is marked as Deployed in Resources, and the step finishes with Deployed carried resources.

If the package cannot be found, the step fails and nothing is changed.

Running a deploy again is safe. Resources that this version of the package has already applied are skipped, so a deploy that stopped halfway can simply be repeated.

Works well with

getAffected and getSignoffs, which prepare the deploy.
absolute, the sign-off that must pass first.
Resources, where packages are deployed and their status is shown.