ves-io-schema-network_interface-API-Replace
On This Page:
Examples of replacing network_interface
Usecase:
Replace network-interface-1
Request using vesctl:
vesctl configuration replace network_interface -i network_interface.yaml
where file network_interface.yaml has following contents (network_interface.ReplaceRequest):
RequestJSON:
{
"metadata": {
"name": "network-interface-1",
"namespace": "system"
},
"spec": {
"ethernet_interface": {
"device": "eth0",
"cluster": {},
"untagged": {},
"dhcp_client": {},
"site_local_inside_network": {},
"mtu": 1500,
"priority": 20,
"is_primary": {}
}
}
}
vesctl yaml response: None
Request using curl:
curl -X 'PUT' -d '{"metadata":{"name":"network-interface-1","namespace":"system"},"spec":{"ethernet_interface":{"device":"eth0","cluster":{},"untagged":{},"dhcp_client":{},"site_local_inside_network":{},"mtu":1500,"priority":20,"is_primary":{}}}}' -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/config/namespaces/system/network_interfaces/network-interface-1'
curl response:
HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Thu, 21 Mar 2024 14:06:16 GMT
Vary: Accept-Encoding
{
}