Create a runbook draft from a published runbook
The Create a runbook draft from a published runbook operation puts a runbook in edit mode. Perform this task on a published runbook, because it does not have a draft.
To publish, use the Publish a draft runbook or Discard a draft runbook operations.
Request
To specify the request, replace <subscription-id> with your subscription ID, <cloud-service-name> with the name of the cloud service to use for making the request, <automation-account-name> with the name of the automation account to use for making the request, and <runbook-name> with the name of the draft runbook to update. Include required URI parameters.
Method |
Request URI |
|---|---|
PUT |
https://management.core.windows.net/<subscription-id>/cloudServices/<cloud-service-name>/resources/automation/~/automationAccounts/<automation-account-name>/runbooks/<runbook-name>/draft/content?api-version=2014-12-08 |
URI Parameters
Parameter |
Description |
|---|---|
api-version |
Required. Must be set to 2014-12-08. |
Request Headers
The request headers in the following table are required.
Request Header |
Description |
|---|---|
x-ms-version |
Specifies the version of the operation. Set to 2013-06-01 or a later version. |
Content-Length |
Must be specified as 0 (zero). |
Request Body
None
Response
Status Code
The operation returns 202 (Accepted) for an asynchronous operation. To determine its current status, issue a GET request to the URL in the Location header contained in the response. Repeat as needed with the URL from each subsequent response until the status code is 200 (OK).
For information about common error codes, see HTTP/1.1 Status Code Definitions.
Response Headers
Request Header |
Description |
|---|---|
x-ms-request-id |
A unique identifier for the current operation. Use this value to determine the current status of an asynchronous operation. |
Response Body
None