<?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 Galaxy Match firewall rules in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-galaxy-match-firewall-rules/m-p/303057#M2089</link>
    <description>&lt;P&gt;A new version of the Ansible role was released just yesterday and one of the changes was to this specific module.&amp;nbsp; I would recommend updating your role and then trying again, it should work.&amp;nbsp; But &lt;CODE&gt;vsys&lt;/CODE&gt; defaults to &lt;CODE&gt;vsys="vsys1"&lt;/CODE&gt; if you don't specify otherwise, so make sure to set it appropriately if you want to run the module against a different vsys.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Dec 2019 22:08:38 GMT</pubDate>
    <dc:creator>gfreeman</dc:creator>
    <dc:date>2019-12-10T22:08:38Z</dc:date>
    <item>
      <title>Ansible Galaxy Match firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-galaxy-match-firewall-rules/m-p/302764#M2088</link>
      <description>&lt;P&gt;Hey Guys,&lt;/P&gt;&lt;P&gt;I am very new to Ansible and was hoping someone could help me with this issue I'm running into. I downloaded and installed ansible galaxy and was testing the following "Match firewall rules".&amp;nbsp;&lt;/P&gt;&lt;P&gt;It works on vsys1 but if any of my firewalls don't have a vsys or the rule is on any other vsys (example vsys 2), i get the following error: "fatal: [test.xyz.com]: FAILED! =&amp;gt; {"changed": false, "msg": "Matched \"test rule\" with \"test security-policy-match destination \"x.x.x.123\" destination-port \"443\" protocol \"6\" source \"10.x.y.z\"\", but wasn't in rulebase"}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's weird that it matches and prints the name of the rule, but fails with "but wasn't in rulebase".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;would appreciate any help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 19:38:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-galaxy-match-firewall-rules/m-p/302764#M2088</guid>
      <dc:creator>manzoorm</dc:creator>
      <dc:date>2019-12-09T19:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Ansible Galaxy Match firewall rules</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-galaxy-match-firewall-rules/m-p/303057#M2089</link>
      <description>&lt;P&gt;A new version of the Ansible role was released just yesterday and one of the changes was to this specific module.&amp;nbsp; I would recommend updating your role and then trying again, it should work.&amp;nbsp; But &lt;CODE&gt;vsys&lt;/CODE&gt; defaults to &lt;CODE&gt;vsys="vsys1"&lt;/CODE&gt; if you don't specify otherwise, so make sure to set it appropriately if you want to run the module against a different vsys.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2019 22:08:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-galaxy-match-firewall-rules/m-p/303057#M2089</guid>
      <dc:creator>gfreeman</dc:creator>
      <dc:date>2019-12-10T22:08:38Z</dc:date>
    </item>
  </channel>
</rss>

