ves-io-schema-network_interface-API-Replace

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=_tmp_go-build243329498_b001_apidocs.test/host=docker-desktop' '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: Fri, 23 Sep 2022 13:13:19 GMT
Vary: Accept-Encoding

{

}