ves-io-schema-registration-CustomAPI-RegistrationConfig
Examples of performing registration CustomAPI RegistrationConfig
Usecase:
Read configuration for registration
Request:
Request using vesctl:
vesctl request rpc registration.CustomAPI.RegistrationConfig -i request.yaml --uri /public/requestConfig --http-method POST
where file request.yaml has following contents:
name: r-4b0b5d92-c23e-4cdd-884e-8d48978fecc8
namespace: system
token: cc3af983-cb5e-4d97-8cc2-55e367566166
vesctl yaml response:
workload:
ce-ver:
params:
param1: abc
Request using curl:
curl -X 'POST' -d '{"namespace":"system","name":"r-4b0b5d92-c23e-4cdd-884e-8d48978fecc8","token":"cc3af983-cb5e-4d97-8cc2-55e367566166"}' -H 'Content-Type: application/json' -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/register/requestConfig'
curl response:
HTTP/1.1 200 OK
Content-Length: 131
Content-Type: application/json
Date: Thu, 21 Mar 2024 14:06:46 GMT
Vary: Accept-Encoding
{
"workload": {
"ce-ver": {
"params": {
"param1": "abc"
},
"app_name": ""
}
},
"hash": ""
}