Examples of replacing site_mesh_group

Usecase:

Replace site-mesh-group-1

Request using vesctl:

vesctl configuration replace site_mesh_group -i site_mesh_group.yaml

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

RequestJSON:

{"metadata":{"name":"site-mesh-group-1","namespace":"system"},"spec":{"type":"SITE_MESH_GROUP_TYPE_SPOKE","tunnel_type":"SITE_TO_SITE_TUNNEL_IPSEC","virtual_site":[{"kind":"virtual_site","name":"vsite-spoke-2"}],"hub":[{"kind":"site_mesh_group","name":"site-mesh-group-hub-2"}]}} `

vesctl yaml response: None

Request using curl:

curl -X 'PUT' -d '{"metadata":{"name":"site-mesh-group-1","namespace":"system"},"spec":{"type":"SITE_MESH_GROUP_TYPE_SPOKE","tunnel_type":"SITE_TO_SITE_TUNNEL_IPSEC","virtual_site":[{"kind":"virtual_site","name":"vsite-spoke-2"}],"hub":[{"kind":"site_mesh_group","name":"site-mesh-group-hub-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/site_mesh_groups/site-mesh-group-1'

curl response:

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

{

}