<?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: knowledge object export in default.meta in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444300#M3939</link>
    <description>&lt;P&gt;Correct. Depending of where I search I don't have the same commands for example. It's like little workbench. &lt;/P&gt;</description>
    <pubDate>Sat, 22 Dec 2018 12:19:47 GMT</pubDate>
    <dc:creator>valiquet</dc:creator>
    <dc:date>2018-12-22T12:19:47Z</dc:date>
    <item>
      <title>knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444295#M3934</link>
      <description>&lt;P&gt;I've only found examples for export=system which is a global export. Can some someone direct me to a docs that shows a defined list of apps or roles I can export to specifically? Or is this not via default/local.meta?&lt;/P&gt;

&lt;P&gt;I know export=none will be app spcific, but I'm after something like export=search which would be my app and search, but nothing else&lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 03:54:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444295#M3934</guid>
      <dc:creator>nickstone</dc:creator>
      <dc:date>2018-12-22T03:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444296#M3935</link>
      <description>&lt;P&gt;You cannot export in other apps. It&lt;CODE&gt;s either private, local or global. On the otherhands ES imports artifacts. I suggest you to set it global but to fine tune the entitlements. Even if it&lt;/CODE&gt;s share globally, it won`t affect others.&lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 10:22:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444296#M3935</guid>
      <dc:creator>valiquet</dc:creator>
      <dc:date>2018-12-22T10:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444297#M3936</link>
      <description>&lt;P&gt;I'm not worried about entitlement, I'd rather not load configuration unnecessarily.&lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 10:41:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444297#M3936</guid>
      <dc:creator>nickstone</dc:creator>
      <dc:date>2018-12-22T10:41:07Z</dc:date>
    </item>
    <item>
      <title>Re: knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444298#M3937</link>
      <description>&lt;P&gt;What is the config?&lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 11:04:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444298#M3937</guid>
      <dc:creator>valiquet</dc:creator>
      <dc:date>2018-12-22T11:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444299#M3938</link>
      <description>&lt;P&gt;I guess this is the bit that was mis-leading me:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;UL&gt;
&lt;LI&gt;Objects that are exported to &lt;STRONG&gt;other apps or&lt;/STRONG&gt; to system context have no change
to their accessibility rules.  Users must still have read access to the
containing app, category, and object, despite the export.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;from:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Defaultmetaconf#default.meta.conf.spec"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Defaultmetaconf#default.meta.conf.spec&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 11:59:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444299#M3938</guid>
      <dc:creator>nickstone</dc:creator>
      <dc:date>2018-12-22T11:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: knowledge object export in default.meta</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444300#M3939</link>
      <description>&lt;P&gt;Correct. Depending of where I search I don't have the same commands for example. It's like little workbench. &lt;/P&gt;</description>
      <pubDate>Sat, 22 Dec 2018 12:19:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/knowledge-object-export-in-default-meta/m-p/444300#M3939</guid>
      <dc:creator>valiquet</dc:creator>
      <dc:date>2018-12-22T12:19:47Z</dc:date>
    </item>
  </channel>
</rss>

