<?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 Limit extra variables passed to ansible tower job in HPE Morpheus Enterprise</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/limit-extra-variables-passed-to-ansible-tower-job/m-p/7247445#M619</link>
    <description>&lt;P&gt;Hello&lt;BR /&gt;
Currently when running an ansible tower job we get around 3k lines of variables parsed from the morpheus instance.&lt;BR /&gt;
Is it possible to only parse a selection of variables.&lt;BR /&gt;
Using variables within custom config just puts the new variables on top of the others.&lt;BR /&gt;
We currently use a python task to workaround this and map the variables in a specific way and call the tower via api.&lt;BR /&gt;
But ideally we want to use the available Tower Integration.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2024 12:19:19 GMT</pubDate>
    <dc:creator />
    <dc:date>2024-10-30T12:19:19Z</dc:date>
    <item>
      <title>Limit extra variables passed to ansible tower job</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/limit-extra-variables-passed-to-ansible-tower-job/m-p/7247445#M619</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;
Currently when running an ansible tower job we get around 3k lines of variables parsed from the morpheus instance.&lt;BR /&gt;
Is it possible to only parse a selection of variables.&lt;BR /&gt;
Using variables within custom config just puts the new variables on top of the others.&lt;BR /&gt;
We currently use a python task to workaround this and map the variables in a specific way and call the tower via api.&lt;BR /&gt;
But ideally we want to use the available Tower Integration.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 12:19:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/limit-extra-variables-passed-to-ansible-tower-job/m-p/7247445#M619</guid>
      <dc:creator />
      <dc:date>2024-10-30T12:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: Limit extra variables passed to ansible tower job</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/limit-extra-variables-passed-to-ansible-tower-job/m-p/7247446#M620</link>
      <description>&lt;P&gt;Hello &lt;A class="mention" href="https://community.hpe.com/u/purpee"&gt;@PurpEE&lt;/A&gt;, I hope you are well today!&lt;/P&gt;
&lt;P&gt;After reviewing, I don’t believe you can select a subset of variables to be passed by the integration.&lt;BR /&gt;
Similar to the Python Tasks, we make them all available, to ensure the user has access to all the information.  Your workaround method is probably the best way, if you are requiring only a specific number of variables be passed via Extra Variables.&lt;/P&gt;
&lt;P&gt;If this is an important feature to you, I’d recommend creating an Idea in our &lt;A href="https://discuss.morpheusdata.com/c/ideas"&gt;Ideas&lt;/A&gt; section of the forums.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 12:55:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/limit-extra-variables-passed-to-ansible-tower-job/m-p/7247446#M620</guid>
      <dc:creator>KoreyG</dc:creator>
      <dc:date>2024-10-30T12:55:55Z</dc:date>
    </item>
  </channel>
</rss>

