The vrf property is present in the GET response schema for /devices/{serial}/managementInterface (both wan1 and wan2 objects), but it is absent from the PUT request body schema.
According to the API behavior, vrf is an accepted optional property in the PUT body -- the API accepts and persists it correctly. This is also reflected in the official API changelog for v1.68.0 which lists:
Optional property vrf Added (wan1)
Optional property vrf Added (wan2)
Steps to reproduce
Check the OpenAPI spec for PUT /devices/{serial}/managementInterface
Compare wan1.properties and wan2.properties between the PUT request body schema and the GET response schema
vrf appears in GET but not in PUT
Expected behavior
The PUT request body schema for wan1 and wan2 should include:
"vrf": {
"type": "object",
"description": "VRF associated with the management interface. If not provided, the default VRF is used.",
"properties": {
"name": {
"type": "string",
"description": "The name of the VRF.",
"x-nullable": true
}
}
}
Actual behavior
vrf is missing from the PUT request body schema for both wan1 and wan2.
The vrf property is present in the GET response schema for /devices/{serial}/managementInterface (both wan1 and wan2 objects), but it is absent from the PUT request body schema.
According to the API behavior, vrf is an accepted optional property in the PUT body -- the API accepts and persists it correctly. This is also reflected in the official API changelog for v1.68.0 which lists:
Optional property vrf Added (wan1)
Optional property vrf Added (wan2)
Steps to reproduce
Check the OpenAPI spec for PUT /devices/{serial}/managementInterface
Compare wan1.properties and wan2.properties between the PUT request body schema and the GET response schema
vrf appears in GET but not in PUT
Expected behavior
The PUT request body schema for wan1 and wan2 should include:
"vrf": {
"type": "object",
"description": "VRF associated with the management interface. If not provided, the default VRF is used.",
"properties": {
"name": {
"type": "string",
"description": "The name of the VRF.",
"x-nullable": true
}
}
}
Actual behavior
vrf is missing from the PUT request body schema for both wan1 and wan2.