<?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: Delete Command Permissions - Specific Index in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246081#M47563</link>
    <description>&lt;P&gt;Using &lt;CODE&gt;|delete&lt;/CODE&gt; depends on ability to search, so you could create a seperate user &amp;amp; role that has only permissions to a single index and includes the &lt;CODE&gt;can_delete&lt;/CODE&gt; role.&lt;/P&gt;

&lt;P&gt;It's not possible to selectively limit &lt;CODE&gt;| delete&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;If your data is changing, it's possibly better suited to the KV Store.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Mar 2016 15:37:29 GMT</pubDate>
    <dc:creator>dturnbull_splun</dc:creator>
    <dc:date>2016-03-11T15:37:29Z</dc:date>
    <item>
      <title>Delete Command Permissions - Specific Index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246080#M47562</link>
      <description>&lt;P&gt;We are working on a utility to selectively push data into a summary index. Of CRUD operations we do not have Delete.&lt;/P&gt;

&lt;P&gt;I would like to have users be able to use delete command against a that summary index, but not others. Is this possible?&lt;/P&gt;

&lt;P&gt;Docs indicate the can_delete role is command specific. Is it possible to allow delete only for a specific index? Maybe clone the can_delete role and give it rights to only to a specific index?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 09:05:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246080#M47562</guid>
      <dc:creator>snoobzilla</dc:creator>
      <dc:date>2020-09-29T09:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Delete Command Permissions - Specific Index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246081#M47563</link>
      <description>&lt;P&gt;Using &lt;CODE&gt;|delete&lt;/CODE&gt; depends on ability to search, so you could create a seperate user &amp;amp; role that has only permissions to a single index and includes the &lt;CODE&gt;can_delete&lt;/CODE&gt; role.&lt;/P&gt;

&lt;P&gt;It's not possible to selectively limit &lt;CODE&gt;| delete&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;If your data is changing, it's possibly better suited to the KV Store.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2016 15:37:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246081#M47563</guid>
      <dc:creator>dturnbull_splun</dc:creator>
      <dc:date>2016-03-11T15:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: Delete Command Permissions - Specific Index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246082#M47564</link>
      <description>&lt;P&gt;Thanks for the info, will forward to my admin.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Mar 2016 14:49:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-Command-Permissions-Specific-Index/m-p/246082#M47564</guid>
      <dc:creator>snoobzilla</dc:creator>
      <dc:date>2016-03-12T14:49:09Z</dc:date>
    </item>
  </channel>
</rss>

