<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [Ansible] Commit in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-commit/m-p/325678#M2283</link>
    <description>&lt;P&gt;If I use "panos_security_rule" to add a rule and I set "commit" to False it does not commit.&amp;nbsp; 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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).&lt;/P&gt;</description>
    <pubDate>Fri, 01 May 2020 15:56:16 GMT</pubDate>
    <dc:creator>gfreeman</dc:creator>
    <dc:date>2020-05-01T15:56:16Z</dc:date>
    <item>
      <title>[Ansible] Commit</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-commit/m-p/323773#M2273</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've noticed that Ansible will commit changes by default, False option doesn't seem to influence it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, if Ansible adds security rule for 10.10.10.1 - it will not be committed.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, I have not been able to make panos_commit module work with "admins" key - all changes are always committed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did anyone perhaps have a similar experience?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Apr 2020 06:47:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-commit/m-p/323773#M2273</guid>
      <dc:creator>atomasovic</dc:creator>
      <dc:date>2020-04-20T06:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: [Ansible] Commit</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-commit/m-p/325678#M2283</link>
      <description>&lt;P&gt;If I use "panos_security_rule" to add a rule and I set "commit" to False it does not commit.&amp;nbsp; 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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).&lt;/P&gt;</description>
      <pubDate>Fri, 01 May 2020 15:56:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-commit/m-p/325678#M2283</guid>
      <dc:creator>gfreeman</dc:creator>
      <dc:date>2020-05-01T15:56:16Z</dc:date>
    </item>
  </channel>
</rss>

