<?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 Leveraging PAN-defined objects within Terrafom in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/leveraging-pan-defined-objects-within-terrafom/m-p/215112#M1672</link>
    <description>&lt;P&gt;A brand new PAN device has pre-defined objects. What is the best method to consume these existing objects? Should I be dumping the PAN objects from the API, and creating Terraform data objects to statically consume? Should I import them into panorama_address/service_objects to manage them within my TF state file?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is Palo Alto planning on scripting this for our consumption. Then when an object gets updated or added, we could consume the new list. It could be kept here: &lt;A href="https://github.com/terraform-providers/terraform-provider-panos" target="_blank"&gt;https://github.com/terraform-providers/terraform-provider-panos&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Tue, 22 May 2018 22:40:11 GMT</pubDate>
    <dc:creator>franklinwong</dc:creator>
    <dc:date>2018-05-22T22:40:11Z</dc:date>
    <item>
      <title>Leveraging PAN-defined objects within Terrafom</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/leveraging-pan-defined-objects-within-terrafom/m-p/215112#M1672</link>
      <description>&lt;P&gt;A brand new PAN device has pre-defined objects. What is the best method to consume these existing objects? Should I be dumping the PAN objects from the API, and creating Terraform data objects to statically consume? Should I import them into panorama_address/service_objects to manage them within my TF state file?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is Palo Alto planning on scripting this for our consumption. Then when an object gets updated or added, we could consume the new list. It could be kept here: &lt;A href="https://github.com/terraform-providers/terraform-provider-panos" target="_blank"&gt;https://github.com/terraform-providers/terraform-provider-panos&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 22 May 2018 22:40:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/leveraging-pan-defined-objects-within-terrafom/m-p/215112#M1672</guid>
      <dc:creator>franklinwong</dc:creator>
      <dc:date>2018-05-22T22:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: Leveraging PAN-defined objects within Terrafom</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/leveraging-pan-defined-objects-within-terrafom/m-p/215113#M1673</link>
      <description>&lt;P&gt;Hi, yeah, that github repo has code that is maintained by Palo Alto Networks employees.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Providing access to the predefined address objects / service objects as a data source seems to be the most appropriate thing to do, as predefined objects are read only.&amp;nbsp; Can you open up an issue against the provider so we can track this feature request?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the mean time, you may not be able to refer to the predefined objects using Terraform resource (or data source) attribute variables, but you can still use the absolute names of these things in your Terraform plan files, and PAN-OS will know if it's supposed to be a predefined object or a user defined object.&lt;/P&gt;</description>
      <pubDate>Tue, 22 May 2018 22:59:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/leveraging-pan-defined-objects-within-terrafom/m-p/215113#M1673</guid>
      <dc:creator>gfreeman</dc:creator>
      <dc:date>2018-05-22T22:59:38Z</dc:date>
    </item>
  </channel>
</rss>

