<?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 Share props.conf into two different apps in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342096#M66400</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;

&lt;P&gt;I am not sure what I am asking for is doable or not but here it is:&lt;/P&gt;

&lt;P&gt;I would like to be able to share some configurations in between apps. For example the field extraction.&lt;/P&gt;

&lt;P&gt;I would have app A with a field extraction up to date and app B "calling" the props.conf file from App A.&lt;/P&gt;

&lt;P&gt;That way any time I am changing things into App A, App B would benefit those enhancements.&lt;/P&gt;

&lt;P&gt;I am not talking about global sharing the knowledge objects here as I don't want those extracted fields to be available in ALL my apps, but only between A and B.&lt;/P&gt;

&lt;P&gt;Is there any way to do this ? any configuration like in App B: &lt;BR /&gt;
include AppB:props.conf&lt;/P&gt;

&lt;P&gt;Something like this?&lt;/P&gt;

&lt;P&gt;Thanks for your help guys!&lt;/P&gt;</description>
    <pubDate>Thu, 20 Apr 2017 15:39:09 GMT</pubDate>
    <dc:creator>llacoste</dc:creator>
    <dc:date>2017-04-20T15:39:09Z</dc:date>
    <item>
      <title>Share props.conf into two different apps</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342096#M66400</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;

&lt;P&gt;I am not sure what I am asking for is doable or not but here it is:&lt;/P&gt;

&lt;P&gt;I would like to be able to share some configurations in between apps. For example the field extraction.&lt;/P&gt;

&lt;P&gt;I would have app A with a field extraction up to date and app B "calling" the props.conf file from App A.&lt;/P&gt;

&lt;P&gt;That way any time I am changing things into App A, App B would benefit those enhancements.&lt;/P&gt;

&lt;P&gt;I am not talking about global sharing the knowledge objects here as I don't want those extracted fields to be available in ALL my apps, but only between A and B.&lt;/P&gt;

&lt;P&gt;Is there any way to do this ? any configuration like in App B: &lt;BR /&gt;
include AppB:props.conf&lt;/P&gt;

&lt;P&gt;Something like this?&lt;/P&gt;

&lt;P&gt;Thanks for your help guys!&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2017 15:39:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342096#M66400</guid>
      <dc:creator>llacoste</dc:creator>
      <dc:date>2017-04-20T15:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Share props.conf into two different apps</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342097#M66401</link>
      <description>&lt;P&gt;I'm afraid it's not possible. The scope of a knowledge object in Splunk (managed by sharing permissions dialog) is  within that app Or all apps.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2017 16:09:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342097#M66401</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-04-20T16:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: Share props.conf into two different apps</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342098#M66402</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Thanks for the answer. &lt;BR /&gt;
I was quite a bit afraid of that, yes... but as I am always told that Splunk is magic and we can do everything... I started believing so ahah!&lt;/P&gt;

&lt;P&gt;Maybe there is a hidden conf we are not aware of...&lt;/P&gt;

&lt;P&gt;I will let this thread one day and see if somebody comes up with a miracle, otherwise I'll close it&lt;/P&gt;

&lt;P&gt;Thanks again for your help.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2017 16:14:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342098#M66402</guid>
      <dc:creator>llacoste</dc:creator>
      <dc:date>2017-04-20T16:14:24Z</dc:date>
    </item>
    <item>
      <title>Re: Share props.conf into two different apps</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342099#M66403</link>
      <description>&lt;P&gt;In /AppB/metadata/default.meta or local.meta in AppB add this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; []
 import = AppA
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;[] likely exists already so just add the import underneath, save and restart.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2017 16:30:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342099#M66403</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-04-20T16:30:31Z</dc:date>
    </item>
    <item>
      <title>Re: Share props.conf into two different apps</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342100#M66404</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
Thanks for the tips, I will try to use that and see if it's working. That would be awesome.&lt;BR /&gt;
Cheers&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 08:35:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Share-props-conf-into-two-different-apps/m-p/342100#M66404</guid>
      <dc:creator>llacoste</dc:creator>
      <dc:date>2017-04-21T08:35:53Z</dc:date>
    </item>
  </channel>
</rss>

