Roll back a policy to a prior revision.
Changed onRestores the content of the specified revision as a new head revision, preserving the full history. The live policy is updated with the prior content and its revision counter is incremented. The description and notes are kept. The rollback is audited. Send the ETag from your read in If-Match to make the write conditional: if the policy, its description, or its notes changed since, nothing is written and the response is 409 with reason policy_changed. Without If-Match the write is not checked against an earlier read. Admins may roll back another user's policy via the owner parameter. Requires the policies:write scope.
Request
- Base URL/ (relative, and the document was published on a file host, not at the API’s origin)
- URL/api/policies/{policyName}/rollback
- AuthHTTP bearer
Path parameters
Query parameters
Headers
Response
Rollback succeeded. Body contains the new revision number, and the ETag header identifies the policy as rolled back.
Changes
- info
added the new optional
headerrequest parameterIf-Match
- info
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info