Delete a specific policy

The ID of the policy needs to follow the namespaced entity ID notation (see Ditto documentation on namespaced entity IDs).

The namespace needs to:

• conform to the reverse domain name notation

The If-Match header, which has to conform to RFC-7232 (Conditional Requests). Common usages are:

• optimistic locking by specifying the ETag from a previous GET response, e.g. If-Match: "rev:4711"
• retrieving or modifying a resource only if it already exists, e.g. If-Match: *

The If-None-Match header, which has to conform to RFC-7232 (Conditional Requests). A common usage scenario is to modify a resource only if it does not yet exist, thus to create it, by specifying If-None-Match: *.

Defines how long the backend should wait for completion of the request, e.g. applied when waiting for requested acknowledgements via the requested-acks param. Can be specified without unit (then seconds are assumed) or together with s, ms or m unit. Example: 42s, 1m.

The default (if omitted) and maximum timeout is 60s. A value of 0 applies fire and forget semantics for the command resulting in setting response-required=false.

Defines whether a response is required to the API call or not - if set to false the response will directly sent back with a status code of 202 (Accepted).

The default (if ommited) response is true.

The policy was successfully deleted.

The request could not be completed. Possible reasons:

• the policyId does not conform to the namespaced entity ID notation (see Ditto documentation on namespaced entity IDs)

The request could not be completed due to missing authentication.

The request could not be completed. Possible reasons:

• the caller has insufficient permissions. You need WRITE permission on the root policy:/ resource, without any revoke in a deeper path of the policy resource.having any revoke.

The request could not be completed. The policy with the given ID or policy referenced in a policy import was not found in the context of the authenticated user.

A precondition for reading or writing the (sub-)resource failed. This will happen for write requests, if you specified an If-Match or If-None-Match header, which fails the precondition check against the current ETag of the (sub-)resource. For read requests, this error may only happen for a failing If-Match header. In case of a failing If-None-Match header for a read request, status 304 will be returned instead.