Closed nabsdcnm closed 2 years ago
@nabsdcnm Thanks for raising the issue. We are discussing the behavior here and will respond soon.
@nabsdcnm We have discussed this internally and this is a valid use case for the merged
case. We will fix this.
@mikewiebe, thank for your reply. Can you please tell me when this fix will be available ? Another question, do you know if the merge in the network module has the same issue ?
@nabsdcnm We currently do not support a free form set of commands for the dcnm_network
module.
We don't have an estimated date for this fix yet but we are finishing up the fix for a different issue and then we will take this up next.
Hi,
This issue was closed but we don't know on which version this issue is fixed. Can we have a reply please ?
Thx a lot for your lights.
Regards.
@nabsdcnm the fix for this issue is available in 2.1.0 and later releases
Community Note
Ansible Version and collection version
ansible version 2.10 cisco.dcnm 1.2.0 and cisco.dcnm 2.0.1
DCNM version
Affected module(s)
Ansible Playbook
Debug Output
Expected Behavior
I expected to add a cli command inside interface "freeform config field" even if there is already other cli commands inside this field.
Actual Behavior
If there is already cli commands inside interface "Freeform Config filed" , the merged state in the playbook replace all the "Freeform Config filed" by the cli in the playbook.
Steps to Reproduce
References