ves-io-schema-infraprotect_configuration-CustomAPI-Mitigate
Examples of performing infraprotect_configuration CustomAPI Mitigate
Usecase:
Change mitigation state for a configured zone
Request:
Request using vesctl:
vesctl request rpc infraprotect_configuration.CustomAPI.Mitigate -i request.yaml --uri /public/namespaces/system/infraprotect_configurations/38b115f3-da21-42d1-a07e-542806b0d96a/mitigate --http-method POST
where file request.yaml has following contents:
namespace: system
status: true
zoneUuid: 38b115f3-da21-42d1-a07e-542806b0d96a
vesctl yaml response:
prefixes:
- 10.1.1.0/24
Request using curl:
curl -X 'POST' -d '{"namespace":"system","zone_uuid":"38b115f3-da21-42d1-a07e-542806b0d96a","status":true}' -H 'Content-Type: application/json' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_2__8qnt6fwd5dvglr1xqq6l8b7w0000gp_T_go-build449658010_b001_apidocs.test/host=C02FN35BMD6R/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/infraprotect/namespaces/system/infraprotect_configurations/38b115f3-da21-42d1-a07e-542806b0d96a/mitigate'
curl response:
HTTP/1.1 200 OK
Content-Length: 41
Content-Type: application/json
Date: Fri, 12 Jan 2024 12:06:23 GMT
Vary: Accept-Encoding
{
"prefixes": [
"10.1.1.0/24"
]
}