<?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 panos_facts Config Sub Set in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-panos-facts-config-sub-set/m-p/380999#M2537</link>
    <description>&lt;P&gt;Circling back here. The panos_op module can be a bad time in trying to parse the output for the variable you want. What I ended up doing was gathering the facts with the panos_facts config subset and then parsing the xml for the info I needed. Find an example below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: copy panfacts into a file&lt;BR /&gt;&amp;nbsp; template:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; src: /etc/ansible/cp_sucks_prod/palo_show_role/templates/panfacts.j2&lt;BR /&gt;&amp;nbsp;&amp;nbsp; dest: /etc/ansible/cp_sucks_prod/palo_show_role/templates/cp_sucks_prod_panfacts.xml&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: Get panorama IP from the xml output&lt;BR /&gt;&amp;nbsp; community.general.xml:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; path: /etc/ansible/cp_sucks_prod/palo_show_role/templates/cp_sucks_prod_panfacts.xml&lt;BR /&gt;&amp;nbsp;&amp;nbsp; xpath: /config/devices/entry[@name='localhost.localdomain']/deviceconfig/system/panorama-server&lt;BR /&gt;&amp;nbsp;&amp;nbsp; content: text&lt;BR /&gt;&amp;nbsp; register: panorama_server_var&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: print panorama var parsed from xml&lt;BR /&gt;&amp;nbsp; debug: var=item.value&lt;BR /&gt;&amp;nbsp; loop: "{{panorama_server_var.matches.0|dict2items}}"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: set Panorama IP address variable.&lt;BR /&gt;&amp;nbsp; set_fact:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; panorama_IP: "{{item.value}}"&lt;BR /&gt;&amp;nbsp; loop: "{{panorama_server_var.matches.0|dict2items}}"&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jan 2021 14:27:51 GMT</pubDate>
    <dc:creator>ngutierrez31</dc:creator>
    <dc:date>2021-01-20T14:27:51Z</dc:date>
    <item>
      <title>Ansible panos_facts Config Sub Set</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-panos-facts-config-sub-set/m-p/380285#M2531</link>
      <description>&lt;P&gt;Good afternoon team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to obtain values such as the Panorama server IP from a firewall to accomplish a project using Ansible and the paloaltonetworks.panos 2.2.0 collection. The panos_facts module with the config subset specified outputs what appears to be xml. What was this outputs intended use?&amp;nbsp; Was it intended to be parsed for registering variables or are we supposed to use the panos_op module to grab any parts of the config we require for variables?&amp;nbsp; I can find no examples of using this output realistically.&amp;nbsp;&amp;nbsp; There are of course many ways to skin the cat so I'm just wondering if anyone is using the panos_facts/gather_subset: config output to do the job?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;-&amp;nbsp; panos_facts:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; provider: '{{ provider }}'&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; gather_subset: ['config']&lt;BR /&gt;&amp;nbsp;&amp;nbsp; register: panfacts_config&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks all,&lt;/P&gt;&lt;P&gt;Nicolas&lt;/P&gt;</description>
      <pubDate>Sun, 17 Jan 2021 01:35:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-panos-facts-config-sub-set/m-p/380285#M2531</guid>
      <dc:creator>ngutierrez31</dc:creator>
      <dc:date>2021-01-17T01:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: Ansible panos_facts Config Sub Set</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-panos-facts-config-sub-set/m-p/380999#M2537</link>
      <description>&lt;P&gt;Circling back here. The panos_op module can be a bad time in trying to parse the output for the variable you want. What I ended up doing was gathering the facts with the panos_facts config subset and then parsing the xml for the info I needed. Find an example below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: copy panfacts into a file&lt;BR /&gt;&amp;nbsp; template:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; src: /etc/ansible/cp_sucks_prod/palo_show_role/templates/panfacts.j2&lt;BR /&gt;&amp;nbsp;&amp;nbsp; dest: /etc/ansible/cp_sucks_prod/palo_show_role/templates/cp_sucks_prod_panfacts.xml&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: Get panorama IP from the xml output&lt;BR /&gt;&amp;nbsp; community.general.xml:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; path: /etc/ansible/cp_sucks_prod/palo_show_role/templates/cp_sucks_prod_panfacts.xml&lt;BR /&gt;&amp;nbsp;&amp;nbsp; xpath: /config/devices/entry[@name='localhost.localdomain']/deviceconfig/system/panorama-server&lt;BR /&gt;&amp;nbsp;&amp;nbsp; content: text&lt;BR /&gt;&amp;nbsp; register: panorama_server_var&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: print panorama var parsed from xml&lt;BR /&gt;&amp;nbsp; debug: var=item.value&lt;BR /&gt;&amp;nbsp; loop: "{{panorama_server_var.matches.0|dict2items}}"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- name: set Panorama IP address variable.&lt;BR /&gt;&amp;nbsp; set_fact:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; panorama_IP: "{{item.value}}"&lt;BR /&gt;&amp;nbsp; loop: "{{panorama_server_var.matches.0|dict2items}}"&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 14:27:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/ansible-panos-facts-config-sub-set/m-p/380999#M2537</guid>
      <dc:creator>ngutierrez31</dc:creator>
      <dc:date>2021-01-20T14:27:51Z</dc:date>
    </item>
  </channel>
</rss>

