Closed smukkavi closed 1 year ago
@smukkavi, Thanks for this SR, we are already working on supporting all the vrf parameters in playbook. It will be part of our upcoming release. There are a bunch of General and Advanced parameters already supported, you can check it out. Thanks
PR in review for this: https://github.com/CiscoDevNet/ansible-dcnm/pull/208
Fixed as part of #208
Community Note
Description
Customer likes to use Ansible to push the configurations to stage them on NDFC (deploy=flase) and then deploy them from NDFC during the maintenance window. It is not ideal to pass certain parameters from Ansible script and the remaining parameters from the NDFC (the parameters that are missing on the Ansible script). The NDFC is to hold the staged policies (from ansible) and then deploy when required. The VRF script (ndfc_vrf ansible script downloaded from cisco.dcnm.dcnm_policy) has limited information to post on the NDFC, it is not possible to supply the following parameters in the script and run the Ansible playbook.
Only the VRF name and VRF id are passed to the NDFC, but following information is missing or not feasible to supply from the script.
Vlan ID, the other tabs in the same VRF definition - General Parameters, Advanced and Route-target tabs
Because of this limitation, there is requirement to login to the NDFC to pass these parameters on the GUI.
New or Affected modules(s):
ndfc_vrf ansible script downloaded from cisco.dcnm.dcnm_policy)
DCNM version
Potential ansible task config
References
Additional context Add any other context or screenshots about the feature request here.