<?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: Option lists : Morpheus API in HPE Morpheus Enterprise</title>
    <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249383#M2557</link>
    <description>&lt;P&gt;Thanks Phillips. Yes we already filter based on the naming policy but I wants to know is there any other way we can use of it.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Jun 2023 11:09:42 GMT</pubDate>
    <dc:creator>Ibrahim-GCC</dc:creator>
    <dc:date>2023-06-13T11:09:42Z</dc:date>
    <item>
      <title>Option lists : Morpheus API</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249381#M2555</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;Will it be possible to show only Linux or windows Instance in the option lists using Morpheus API instance?&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;
Ibrahim K&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 09:03:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249381#M2555</guid>
      <dc:creator>Ibrahim-GCC</dc:creator>
      <dc:date>2023-06-13T09:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: Option lists : Morpheus API</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249382#M2556</link>
      <description>&lt;P&gt;If your naming policy includes the type, then yes this would be very simple to do in the translation script:&lt;/P&gt;
&lt;PRE style="background : #f0f1f2;"&gt;&lt;CODE class="lang-auto"&gt;results = [];
for(let i=0; i&amp;lt; data.length; i++) {
  // linux only
  if (data[i].name.toLowerCase().includes("linux")) {
  	results.push({name: data[i].name, value: data[i].value});
  }
}
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;If not it would be difficult to determine that based on the data in the built-in instances call which you can &lt;A href="https://docs.morpheusdata.com/en/latest/library/options/option_lists.html?highlight=input%20list#morpheus-api-option-list-fields"&gt;find here&lt;/A&gt;.  Probably need to make REST request to the API.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 10:52:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249382#M2556</guid>
      <dc:creator>Ollie-Phillips</dc:creator>
      <dc:date>2023-06-13T10:52:40Z</dc:date>
    </item>
    <item>
      <title>Re: Option lists : Morpheus API</title>
      <link>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249383#M2557</link>
      <description>&lt;P&gt;Thanks Phillips. Yes we already filter based on the naming policy but I wants to know is there any other way we can use of it.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 11:09:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-morpheus-enterprise/option-lists-morpheus-api/m-p/7249383#M2557</guid>
      <dc:creator>Ibrahim-GCC</dc:creator>
      <dc:date>2023-06-13T11:09:42Z</dc:date>
    </item>
  </channel>
</rss>

