The metal_connection module was only validating the value of vlans based on the selected redundancy. As a result, invalid values for vrfs would not be caught, and users creating a VRF-based Metal connection would be force to specify a stub value for vlans instead of omitting it entirely.
This updates the metal_connection module to enforce that the user specifies only one of vlans or vrfs, and that the parameter they specify only has 1 element if they are creating a non-redundant connection.
The metal_connection module was only validating the value of
vlans
based on the selected redundancy. As a result, invalid values forvrfs
would not be caught, and users creating a VRF-based Metal connection would be force to specify a stub value forvlans
instead of omitting it entirely.This updates the metal_connection module to enforce that the user specifies only one of
vlans
orvrfs
, and that the parameter they specify only has 1 element if they are creating a non-redundant connection.