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
Since #141 allows for vlan to be defined (as nni_vlan, vlan_id, also vrf_id), it is fine that the user will receive a 422 from the API server prompting them to add vlan in their Ansible configuration.
The field should be denoted as required in Ansible to match the API expectation.
There is an upcoming requirement for VLAN in the requests: https://feedback.equinixmetal.com/changelog/virtual-circuits-will-require-vlans-on-feb-29-2024
Since #141 allows for
vlan
to be defined (asnni_vlan
,vlan_id
, alsovrf_id
), it is fine that the user will receive a422
from the API server prompting them to addvlan
in their Ansible configuration.The field should be denoted as required in Ansible to match the API expectation.
Originally posted by @displague in #141 (comment)
The text was updated successfully, but these errors were encountered: