Create a new Runbook or clone an existing Runbook.

The ID of an existing database runbook to copy. Cloning brings across the source runbook's settings, its process and steps, and any project triggers that target it. The source runbook's tags come across too, unless you supply RunbookTags. Leave unset to create a runbook from scratch, which starts with an empty process.

What a run does when a step fails. One of 'EnvironmentDefault' (follow the target environment's setting), 'Off' (fail the run immediately, the default), or 'On' (pause the run and wait for someone to choose whether to retry, ignore or abort).

Which environments the runbook may be run in. One of 'All' (every environment in the space, the default), 'Specified' (only the environments listed in Environments), or 'FromProjectLifecycles' (only the environments used by the project's lifecycles).

Re-download every package on each run instead of reusing the copy already cached on the deployment target.

Whether the runbook can be run for tenants. One of 'Untenanted' (untenanted runs only, the default), 'Tenanted' (a tenant must be supplied for every run), or 'TenantedOrUntenanted' (either is allowed).

The ID of the project to create the runbook in. Must be a project that stores its runbooks in the Octopus database.

Leave unset. A snapshot can only be published after the runbook exists and has a process.

Leave unset. Octopus creates an empty runbook process for the new runbook and links it automatically.

A short URL-friendly identifier for the runbook, unique within the project. Generated from the name when omitted.