Open chris-tomkins-flexgrid opened 4 months ago
I think we may be looking at needing to have to convert the modules over to a resource model style module with this. So that we can give the options on the modules to support declarative models (the way it is today) and the other idea of supporting of merging data together, which would be taking what is there already, and adding to it rather than just making it appear as declared.
Thanks @jvanderaa. So it feels like in the near term, the only solution here is to make a separate direct API call to handle tags, without using the actual Ansible module?
And, for the long term resolution - sounds reasonable.
It would be a 2 or 3 steps.
Task 1: Grab the current tags that the object has (when it has already been created - yep, this isn't ideal) Task 2: Update the tags
It's really a place at which point that tags and Ansible have a few different ideas.
ISSUE TYPE
SOFTWARE VERSIONS
pynautobot
2.2.0
Ansible:
2.16.0
Nautobot:
2.2.4
Collection:
5.2.1
SUMMARY
Adding tags on a record optionally shouldn't remove existing tags
STEPS TO REPRODUCE
EXPECTED RESULTS
I would expect to optionally be able to specify whether tags should be overwritten or additive.
ACTUAL RESULTS
Other useful tags unrelated to this Ansible play were removed: