ves-io-schema-oidc_provider-CustomAPI-Replace
Examples of performing oidc_provider CustomAPI Replace
Usecase:
Replace google provider
Request:
Request using vesctl:
vesctl request rpc oidc_provider.CustomAPI.Replace -i request.yaml --uri /public/custom/namespaces/documentation/oidc_providers/google-oidc --http-method POST
where file request.yaml has following contents:
namespace: documentation
spec:
googleOidcSpecType:
clientId: new test client id
clientSecret: client-secret
hostedDomain: domain-new
providerType: GOOGLE
vesctl yaml response:
{}
Request using curl:
curl -X 'POST' -d '{"namespace":"documentation","spec":{"provider_type":"GOOGLE","google_oidc_spec_type":{"client_id":"new test client id","client_secret":"client-secret","hosted_domain":"domain-new"}}}' -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/web/custom/namespaces/documentation/oidc_providers/google-oidc'
curl response:
HTTP/1.1 200 OK
Content-Length: 23
Content-Type: application/json
Date: Thu, 21 Mar 2024 14:06:31 GMT
Vary: Accept-Encoding
{
"err": "EUNKNOWN"
}