ves-io-schema-secret_policy_rule-API-Replace
On This Page:
Examples of replacing secret_policy_rule
Usecase:
Replace secret-policy-rule-1
Request using vesctl:
vesctl configuration replace secret_policy_rule -i secret_policy_rule.yaml
where file secret_policy_rule.yaml has following contents (secret_policy_rule.ReplaceRequest):
RequestJSON:
{"metadata":{"name":"secret-policy-rule-1","namespace":"documentation"},"spec":{"action":"ALLOW","client_name_matcher":{"regex_values":["rakar\.re(\d)*\.int\.ves\.io"]}}}
`
vesctl yaml response: None
Request using curl:
curl -X 'PUT' -d '{"metadata":{"name":"secret-policy-rule-1","namespace":"documentation"},"spec":{"action":"ALLOW","client_name_matcher":{"regex_values":["rakar\.re(\d)*\.int\.ves\.io"]}}}' -H 'X-Volterra-Useragent: v1/pgm=_tmp_go-build1372770011_b001_apidocs.test/host=docker-desktop' 'https://acmecorp.console.ves.volterra.io/api/secret_management/namespaces/documentation/secret_policy_rules/secret-policy-rule-1'
curl response:
HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Thu, 28 Jul 2022 12:11:53 GMT
Vary: Accept-Encoding
{
}