ves-io-schema-network_connector-API-Replace

Examples of replacing network_connector

Usecase:

Replace connect-in-out to now update no proxy to do forward proxy between inside network and outside network

Request using vesctl:

vesctl configuration replace network_connector -i network_connector.yaml

where file network_connector.yaml has following contents (network_connector.ReplaceRequest):

RequestJSON:

{"metadata":{"name":"connect-in-out","namespace":"system"},"spec":{"sli_to_slo_snat":{"default_gw_snat":{},"interface_ip":{}},"enable_forward_proxy":{"max_connect_attempts":2}}} `

vesctl yaml response: None

Request using curl:

curl -X 'PUT' -d '{"metadata":{"name":"connect-in-out","namespace":"system"},"spec":{"sli_to_slo_snat":{"default_gw_snat":{},"interface_ip":{}},"enable_forward_proxy":{"max_connect_attempts":2}}}' -H 'X-Volterra-Useragent: v1/pgm=_tmp_go-build1372770011_b001_apidocs.test/host=docker-desktop' 'https://acmecorp.console.ves.volterra.io/api/config/namespaces/system/network_connectors/connect-in-out'

curl response:

HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Thu, 28 Jul 2022 12:11:00 GMT
Vary: Accept-Encoding

{

}