ves-io-schema-pbac-addon_service-API-Get

Examples of getting addon_service

Usecase:

Get addon-service1

Request using vesctl:

vesctl configuration get addon_service addon-service1 --namespace documentation

vesctl yaml response:

Request using curl:

curl -X 'GET' -H 'X-Volterra-Useragent: v1/pgm=_tmp_go-build038462651_b001_apidocs.test/host=docker-desktop' 'https://acmecorp.console.ves.volterra.io/api/web/namespaces/documentation/addon_services/addon-service1?response_format=0'

curl response:

HTTP/1.1 404 Not Found
Content-Length: 397
Content-Type: application/json
Date: Wed, 12 Jan 2022 14:49:55 GMT
Vary: Accept-Encoding

{"code":5,"details":[{"type_url":"type.googleapis.com/ves.io.stdlib.server.error.Error","value":"\u0012vGetResource: ves.io.schema.pbac.addon_service.Object.default: Key acmecorp/documentation/addon-service1 does not exist\u001a62022-01-12 14:49:55.2549604 +0000 UTC m=+144.988340501"}],"message":"ves.io.schema.pbac.addon_service.Object: addon-service1 does not exist in namespace documentation"}