You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vlans can be facility based, but the current metal_vlan_info code
doesn't handle that case - it fails since a facility based vlan doesn't
have the metro field, which is treated as required by the
VLAN_RESPONSE_ATTRIBUTE_MAP.
this PR changes the metro attribute to be optional, and adds a new
optional attribute for the facility, so it can handle both cases
```
{
"description": "native vlan",
"facility": { <<<
"href": "/metal/v1/facilities/d2a72094-26c9-4372-8d65-051424bc370a",
"id": "d2a72094-26c9-4372-8d65-051424bc370a"
},
"id": "abcd",
"metro": "",
"vxlan": 1004
},
{
"description": "Public NAT",
"facility": "",
"id": "abcd",
"metro": { <<<
"href": "/metal/v1/locations/metros/d3d6b29f-042d-43b7-b3ce-0bf53d5754ca",
"id": "d3d6b29f-042d-43b7-b3ce-0bf53d5754ca"
},
"vxlan": 1004
},
```
addresses #195
SUMMARY
when running metal_vlan_info task, the task returns an error if there is a facility based vlan that does not have the metro field set.
ISSUE TYPE
COMPONENT NAME
metal_vlan_info
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
mac
STEPS TO REPRODUCE
EXPECTED RESULTS
i expected the task to return a list of vlans for a specific project
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: