ves-io-schema-forwarding_class-API-Replace

Examples of replacing forwarding_class

Usecase:

Replace forwarding-class-1, that now sends traffic on interfaces with priority 1,2,3 and apply policer-1

Request using vesctl:

vesctl configuration replace forwarding_class -i forwarding_class.yaml

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

RequestJSON:

{
    "metadata": {
        "name": "forwarding-class-1",
        "namespace": "documentation"
    },
    "spec": {
        "interface_group": "INTERFACE_GROUP1",
        "no_marking": {},
        "dscp_based_queue": {},
        "policer": {
            "namespace": "documentation",
            "name": "policer-1"
        }
    }
}

vesctl yaml response: None

Request using curl:

curl -X 'PUT' -d '{"metadata":{"name":"forwarding-class-1","namespace":"documentation"},"spec":{"interface_group":"INTERFACE_GROUP1","no_marking":{},"dscp_based_queue":{},"policer":{"namespace":"documentation","name":"policer-1"}}}' -H 'X-Volterra-Useragent: v1/pgm=_tmp_go-build243329498_b001_apidocs.test/host=docker-desktop' 'https://acmecorp.console.ves.volterra.io/api/config/namespaces/documentation/forwarding_classs/forwarding-class-1'

curl response:

HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Fri, 23 Sep 2022 13:12:13 GMT
Vary: Accept-Encoding

{

}