<?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: Variables available in input app in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92131#M23760</link>
    <description>&lt;P&gt;That solution is simple and scalable. I don't see anything bad with it.&lt;BR /&gt;
Actually, I need the cert for at least two different apps, so this would save me some typing. Of course, there will be a dependency from one app to the other, but I should be able to work with that.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 15 Apr 2013 08:52:49 GMT</pubDate>
    <dc:creator>echalex</dc:creator>
    <dc:date>2013-04-15T08:52:49Z</dc:date>
    <item>
      <title>Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92127#M23756</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I need to reference a file distributed by an input app from within the app itself (outputs.conf). I need to configure a specific receiver with a specific certificate with this app.&lt;/P&gt;

&lt;P&gt;I've tried specified a relative path, but it doesn't seem to work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# first try:
sslRootCAPath = specific-cert.pem
# second try:
sslRootCAPath = ./specific-cert.pem
# third try (copied it first to another dir called certs)
sslRootCAPath = ./certs/specific-cert.pem
# fourth and only successful try:
$SPLUNK_HOME/etc/apps/the_specific_app_directory/certs/specific-cert.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, I'm not happy with this, since the name of the directory may change and I may copy this configuration to other apps as well.&lt;/P&gt;

&lt;P&gt;So, is there a generic way of referencing the app's directory? Based on the scripted inputs in the Splunk_TA_nix configuration, I thought a dot might work, but it does not seem to work.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:43:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92127#M23756</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2020-09-28T13:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92128#M23757</link>
      <description>&lt;P&gt;You can create an app which contains the outputs.conf and the certificates. Even if you specify the path like in your fourth example, you can still have control over it through Deployment Server. &lt;/P&gt;

&lt;P&gt;Using DS the directory will not change unless you deploy it so, and then the certs will go with it. &lt;/P&gt;

&lt;P&gt;Perhaps I've misunderstood your problem.&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;UPDATE:&lt;/P&gt;

&lt;P&gt;Probably bad for a number of reasons I don't have energy to think about right now...but I guess you could make more than one app. &lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;A generic &lt;CODE&gt;CertsApp&lt;/CODE&gt; which can be deployed as you like containing several certs.&lt;/LI&gt;
&lt;LI&gt;One (or more) apps that uses certs in the &lt;CODE&gt;CertsApp&lt;/CODE&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;That would let you reference the certificates fairly statically from whatever &lt;CODE&gt;outputs.conf&lt;/CODE&gt; you want.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;outputs.conf&lt;/CODE&gt; in &lt;CODE&gt;/etc/apps/blah/local&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sslRootCAPath = $SPLUNK_HOME/etc/apps/CertsApp/local/certs/certificate_1.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2013 14:41:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92128#M23757</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-04-12T14:41:03Z</dc:date>
    </item>
    <item>
      <title>Re: Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92129#M23758</link>
      <description>&lt;P&gt;Hi. Yep, that is exactly what I'm doing, but I would like to point to the certificate without using the entire name of the app.&lt;/P&gt;

&lt;P&gt;Something like&lt;BR /&gt;
     sslRootCAPath = $APP_DIRECTORY/certs/specific-cert.pem&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2013 14:43:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92129#M23758</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2013-04-12T14:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92130#M23759</link>
      <description>&lt;P&gt;update above.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2013 15:07:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92130#M23759</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-04-12T15:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92131#M23760</link>
      <description>&lt;P&gt;That solution is simple and scalable. I don't see anything bad with it.&lt;BR /&gt;
Actually, I need the cert for at least two different apps, so this would save me some typing. Of course, there will be a dependency from one app to the other, but I should be able to work with that.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2013 08:52:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92131#M23760</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2013-04-15T08:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: Variables available in input app</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92132#M23761</link>
      <description>&lt;P&gt;Well - glad you like it. I was more concerned with having a lot of certs lying around on servers that weren't using them.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2013 09:43:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Variables-available-in-input-app/m-p/92132#M23761</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-04-15T09:43:47Z</dc:date>
    </item>
  </channel>
</rss>

