/metadata_cascade_policiesCreate metadata cascade policy
Creates a new metadata cascade policy that applies a given metadata template to a given folder and automatically cascades it down to any files within that folder.
In order for the policy to be applied a metadata instance must first be applied to the folder the policy is to be applied to.
- RetriesRetries up to 2×, 500ms backoff, 30s timeout.
A 400 is returned: Returns an error when any of the parameters are not in a valid format.
-
bad_request- Either thescope,templateKey, orfolder_idare not in a valid format. A 403 is returned: Returns an error when trying to apply a policy to a restricted folder, for example the root folder with ID0. -
forbidden- Although the folder ID was valid and the user has access to the folder, the policy could not be applied to this folder. A 404 is returned: Returns an error when the template or folder can not be found, or when the user does not have access to the folder or template. -
instance_tuple_not_found- The template could not be found or the user does not have access to the template. -
not_found- The folder could not be found or the user does not have access to the folder. A 409 is returned: Returns an error when a policy for this folder and template is already in place. -
tuple_already_exists- A cascade policy for this combination offolder_id,scopeandtemplateKeyalready exists. Any other status is an error: An unexpected client error.