04-19-2020 11:47 PM
Hello,
I've noticed that Ansible will commit changes by default, False option doesn't seem to influence it.
For example, if Ansible adds security rule for 10.10.10.1 - it will not be committed.
Next run, adding rule for 10.10.10.2, will commit the rule added for 10.10.10.1, and leave rules for 10.10.10.2.
Additionally, I have not been able to make panos_commit module work with "admins" key - all changes are always committed.
Did anyone perhaps have a similar experience?
Thank you.
Best regards.
05-01-2020 08:56 AM
If I use "panos_security_rule" to add a rule and I set "commit" to False it does not commit. Also the "admins" param requires that your PAN-OS supports that feature (I think it went in around 8.0 timeframe), so you need to be running that or later for that to work.
I guess just make sure you're running a new enough version of PAN-OS and that you're using the Palo Alto Networks Ansible collection (or the role if you're not running Ansible 2.9 or later).
05-01-2020 08:56 AM
If I use "panos_security_rule" to add a rule and I set "commit" to False it does not commit. Also the "admins" param requires that your PAN-OS supports that feature (I think it went in around 8.0 timeframe), so you need to be running that or later for that to work.
I guess just make sure you're running a new enough version of PAN-OS and that you're using the Palo Alto Networks Ansible collection (or the role if you're not running Ansible 2.9 or later).
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
