Closed danischm closed 2 weeks ago
I've noticed the API /vteppolicies
is designed to support in future many VTEPs per device. The same is true for 7.2.5 WebUI. I'd keep that design constraint in provider as well.
Thus, I'd name it fmc_device_vtep_policy
instead of fmc_device_vtep
if you have no objection. The fmc_device_vtep_policy.example.vtep_entries
will be constrained to hold max 1 min 0 elements for now.
sounds good
API: /api/fmc_config/v1/domain/{domainUUID}/devices/devicerecords/{containerUUID}/vteppolicies