<?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: What is the replacement for the deprecated Python call entity.setEntity? in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207629#M2769</link>
    <description>&lt;P&gt;Thanks for the tip!&lt;/P&gt;</description>
    <pubDate>Wed, 02 Nov 2016 22:07:59 GMT</pubDate>
    <dc:creator>Vidd</dc:creator>
    <dc:date>2016-11-02T22:07:59Z</dc:date>
    <item>
      <title>What is the replacement for the deprecated Python call entity.setEntity?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207625#M2765</link>
      <description>&lt;P&gt;I see in the list of deprecated features that entity.setEntity has been deprecated (some time ago).&lt;/P&gt;

&lt;P&gt;What is the recommended alternative for storing the password securely when using a modular input and setup.xml screen?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 17:36:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207625#M2765</guid>
      <dc:creator>Vidd</dc:creator>
      <dc:date>2016-11-02T17:36:34Z</dc:date>
    </item>
    <item>
      <title>Re: What is the replacement for the deprecated Python call entity.setEntity?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207626#M2766</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/182783"&gt;@Vidd&lt;/a&gt;,  The new method of storing password is the &lt;STRONG&gt;passwordstore&lt;/STRONG&gt; which is detailed in &lt;A href="http://dev.splunk.com/view/python-sdk/SP-CAAAEJ6" target="_blank"&gt;How to work with users, roles, and storage passwords using the Splunk SDK for Python&lt;/A&gt;.  A good example is of working with the &lt;STRONG&gt;passwordstore&lt;/STRONG&gt; is the &lt;A href="https://github.com/splunk/splunk-add-on-jira-alerts" target="_blank"&gt;splunk-add-on-jira-alerts&lt;/A&gt; built by Splunk.  While the example is for an alert it can easily be converted for a modular input.  You will need to obtain the auth key inside your modular input which is a property available in &lt;STRONG&gt;self&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Take a close look at splunk-add-on-jira-alerts/bin/jira_alerts_install_endpoint.py for the setup view and splunk-add-on-jira-alerts/bin/jira_helpers.py.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 11:39:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207626#M2766</guid>
      <dc:creator>bmacias84</dc:creator>
      <dc:date>2020-09-29T11:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: What is the replacement for the deprecated Python call entity.setEntity?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207627#M2767</link>
      <description>&lt;P&gt;Thank you so much for the reference and example. Very much appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 21:37:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207627#M2767</guid>
      <dc:creator>Vidd</dc:creator>
      <dc:date>2016-11-02T21:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: What is the replacement for the deprecated Python call entity.setEntity?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207628#M2768</link>
      <description>&lt;P&gt;Also setup.xml in will be deprecated in the future, but no telling when.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 21:41:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207628#M2768</guid>
      <dc:creator>bmacias84</dc:creator>
      <dc:date>2016-11-02T21:41:50Z</dc:date>
    </item>
    <item>
      <title>Re: What is the replacement for the deprecated Python call entity.setEntity?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207629#M2769</link>
      <description>&lt;P&gt;Thanks for the tip!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 22:07:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/What-is-the-replacement-for-the-deprecated-Python-call-entity/m-p/207629#M2769</guid>
      <dc:creator>Vidd</dc:creator>
      <dc:date>2016-11-02T22:07:59Z</dc:date>
    </item>
  </channel>
</rss>

