Load a policy
Adds data to the existing Conjur policy. Deletions are not allowed. Any policy objects that exist on the server but are omitted from the policy file will not be deleted and any explicit deletions in the policy file will result in an error.
Entity IDs must be URL-encoded. |
URI
|
Any identifier included in the URL must be URL-encoded to be recognized by the Conjur API.
Examples
Identifier |
URL-Encoded |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Permissions required
create
privilege on the policy.
Example with curl
Suppose you have a policy to load in /tmp/policy.yml
(such as the sample one provided below).
|
Request Body
The request body should be a policy file. For example:
|
Response
Code |
Description |
---|---|
201 |
The policy was extended successfully. |
401 |
The request lacks valid authentication credentials. |
403 |
The authenticated user lacks the necessary privilege |
404 |
The policy referred to a role or resource that does not exist in the specified account. |
409 |
Policy load already in progress, retry after a delay. |
422 |
The request body was empty or the policy was not valid YAML or the policy includes a deletion. |
Example URI
POST
|
URI Parameters
Parameter |
Type |
Mandatory |
Description |
---|---|---|---|
account |
String |
Yes |
Organization account name.
|
identifier |
String |
Yes |
id of the policy to extend
|
Response 201
Headers
|
Body
|