ves-io-schema-secret_policy-API-Replace
On This Page:
Examples of replacing secret_policy
Usecase:
Replace secret-policy-1
Request using vesctl:
vesctl configuration replace secret_policy -i secret_policy.yaml
where file secret_policy.yaml has following contents (secret_policy.ReplaceRequest):
RequestJSON:
{
"metadata": {
"name": "secret-policy-1",
"namespace": "documentation"
},
"spec": {
"decrypt_cache_timeout": "604800s",
"legacy_rule_list": {
"rules": [
{
"kind": "secret_policy_rule",
"name": "secret-policy-rule-3"
},
{
"kind": "secret_policy_rule",
"name": "secret-policy-rule-4"
}
]
}
}
}
vesctl yaml response: None
Request using curl:
curl -X 'PUT' -d '{"metadata":{"name":"secret-policy-1","namespace":"documentation"},"spec":{"decrypt_cache_timeout":"604800s","legacy_rule_list":{"rules":[{"kind":"secret_policy_rule","name":"secret-policy-rule-3"},{"kind":"secret_policy_rule","name":"secret-policy-rule-4"}]}}}' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_2__8qnt6fwd5dvglr1xqq6l8b7w0000gp_T_go-build3109416560_b001_apidocs.test/host=C02FN35BMD6R/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/secret_management/namespaces/documentation/secret_policys/secret-policy-1'
curl response:
HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Thu, 21 Mar 2024 14:06:56 GMT
Vary: Accept-Encoding
{
}