update script
Deploys a new version of the script at path, which must already hold one. The body's path is the destination: the same path leaves the script where it is, a different one moves it there and archives the old path.
Path parameters
Request body
The hash of the version this one supersedes: deploying with it archives that version and chains the new one onto its history, and a path differing from the superseded version's moves the script there.
When true, the backend resolves the parent to the current deployed head for this path within the transaction (ignoring parent_hash), instead of failing with a "lineage must be linear" error when the supplied parent_hash is stale.
If set, delete the job's args, result and logs after this many seconds following job completion
Authorization identity to run as: u/{username}, g/{group}, or a bare email when the username is itself email-shaped. Supply this or on_behalf_of_email; when only the address is given it is resolved to the account it names, and an address naming nobody is rejected. A pair that disagrees is rejected.
When true and the caller is a member of the 'wm_deployers' group, preserves the original on_behalf_of_email / on_behalf_of pair instead of overwriting it with the caller's own identity.
Additional script modules keyed by relative file path
When true (set by the CLI / git sync), deploying this script does not delete an existing user draft at the same path.
Response
new script version created