Runbook Exec
Start a execution using a Runbook as input. If the connection has a JIRA issue template configured, it will create a JIRA issue.
Body
The request body resource
Connection name to execute the runbook against
"pgdemo"
The relative path name of the runbook file from the git source
"myrunbooks/run-backup.runbook.sql"
Repository name where the runbook is located
"github.com/myorg/myrepo"
Additional arguments to pass down to the connection
["--verbose"]External workflow/task id to group related sessions
"task-12345"
Environment Variables that will be included in the runtime
- { envvar:[env-key]: [base64-val] } - Expose the value as environment variable
- { filesystem:[env-key]: [base64-val] } - Expose the value as a temporary file path creating the value in the filesystem
{
"envvar": "PASSWORD:MTIz",
"filesystem": "SECRET_FILE:bXlzZWNyZXQ="
}Jira fields to create a Jira issue
Metadata attributes to add in the session
The parameters of the runbook. It must match with the declared attributes
{ "amount": "10", "wallet_id": "6736" }The commit sha reference to obtain the file
"20320ebbf9fc612256b67dc9e899bbd6e4745c77"
Batch identifier to group sessions that were executed simultaneously
"batch-abc-123"
Response
The execution has finished
The amount of time the execution took in miliseconds
5903
The shell exit code, any non zero code means an error
- 0 - Linux success exit code
- -2 - internal gateway code that means it was unable to obtain a valid exit code number from the agent outcome packet
- 254 - internal agent code that means it was unable to obtain a valid exit code number from the process
1
Inform if the connection has review enabled
false
Output contains an utf-8 output containing the outcome of the ad-hoc execution
Status reports if the outcome of the execution
- success - The execution was executed with success
- failed - In case of internal error or when the agent returns an exit code greater than 0 or different than -2
- running - The execution may still be running.
success, failed, running "failed"
Each execution creates a unique session id
"5701046A-7B7A-4A78-ABB0-A24C95E6FE54"
If the `output`` field is truncated or not
false