I am developing an Ansible Playbook automating IPAM.
While using the infoblox.nios_modules I noticed a weird behaviour. After creating a hostrecord with an IP-address x and a hostname, I executed the playbook again now with a different IP-address y and the same hostname. The secon hostrecord was placed in the IP-Adress y but also the first hostrecord was placed there. Also the extra attributes of the first hostrecord changed.
This was already described in #108
I fixed the problem in the commit 58cb936c8e76bd71280af3e5c70f55ca31ddd6fe. This only fixes the problem if the if_obj_type is "NIOS_HOST_RECORD".
A general fix is going to be given in the PR: Bugfix/second record with same name option 2. I can not forsee if the general fix influences any other use case though.
I am developing an Ansible Playbook automating IPAM. While using the infoblox.nios_modules I noticed a weird behaviour. After creating a hostrecord with an IP-address x and a hostname, I executed the playbook again now with a different IP-address y and the same hostname. The secon hostrecord was placed in the IP-Adress y but also the first hostrecord was placed there. Also the extra attributes of the first hostrecord changed.
This was already described in #108
I fixed the problem in the commit 58cb936c8e76bd71280af3e5c70f55ca31ddd6fe. This only fixes the problem if the if_obj_type is "NIOS_HOST_RECORD". A general fix is going to be given in the PR: Bugfix/second record with same name option 2. I can not forsee if the general fix influences any other use case though.