<?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: Manipulate conf file through Splunk/Rest API in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91571#M1302</link>
    <description>&lt;P&gt;How did you issue the curl call?&lt;/P&gt;

&lt;P&gt;I created a new config 'myconfig' &lt;EM&gt;and&lt;/EM&gt; a corresponding 'myconfig.conf.spec' in the README subdir of my app. After that, I was able to &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;curl -k -u admin:pass &lt;A href="https://127.0.0.1:8089/servicesNS/admin/fire_brigade/configs/conf-myconfig"&gt;https://127.0.0.1:8089/servicesNS/admin/fire_brigade/configs/conf-myconfig&lt;/A&gt;&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I only mention the README subdir because I didn't try it without. Did you get an error from the curl call? I got an XML response that contained the config key. Note also that I restarted Splunk after adding the config file and the README/myconfig.conf.spec. I'm not sure if that was required, but....&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2013 13:15:45 GMT</pubDate>
    <dc:creator>sowings</dc:creator>
    <dc:date>2013-10-10T13:15:45Z</dc:date>
    <item>
      <title>Manipulate conf file through Splunk/Rest API</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91568#M1299</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Is there any experience around to be shared concerning how to programmatically manipulate (read, update) through Splunk API or REST API a custom conf file (say "myapp.conf"). &lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 20:37:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91568#M1299</guid>
      <dc:creator>klausJohan</dc:creator>
      <dc:date>2013-10-09T20:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: Manipulate conf file through Splunk/Rest API</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91569#M1300</link>
      <description>&lt;P&gt;I'd start with trying the &lt;CODE&gt;| rest&lt;/CODE&gt; search command in Splunk. It would at least tell you if your custom config file is &lt;EM&gt;reachable&lt;/EM&gt; by the REST endpoint. Try: &lt;CODE&gt;| rest /services/configs/conf-myapp&lt;/CODE&gt; (or optionally, constrain the app and user: &lt;CODE&gt;| rest /servicesNS/admin/myapp/configs/conf-myapp&lt;/CODE&gt;).&lt;/P&gt;

&lt;P&gt;Note that any POSTs to define settings don't have restrictions on the keys, that's up to your app to define. More docs about the POST (and an example) can be found here:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/RESTAPI/RESTconfig"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/RESTAPI/RESTconfig&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 20:46:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91569#M1300</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-10-09T20:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Manipulate conf file through Splunk/Rest API</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91570#M1301</link>
      <description>&lt;P&gt;Yes, through "| rest ..." I can see my conf file. But the get/post request with curl or from the browser return no result&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 08:08:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91570#M1301</guid>
      <dc:creator>klausJohan</dc:creator>
      <dc:date>2013-10-10T08:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: Manipulate conf file through Splunk/Rest API</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91571#M1302</link>
      <description>&lt;P&gt;How did you issue the curl call?&lt;/P&gt;

&lt;P&gt;I created a new config 'myconfig' &lt;EM&gt;and&lt;/EM&gt; a corresponding 'myconfig.conf.spec' in the README subdir of my app. After that, I was able to &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;curl -k -u admin:pass &lt;A href="https://127.0.0.1:8089/servicesNS/admin/fire_brigade/configs/conf-myconfig"&gt;https://127.0.0.1:8089/servicesNS/admin/fire_brigade/configs/conf-myconfig&lt;/A&gt;&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I only mention the README subdir because I didn't try it without. Did you get an error from the curl call? I got an XML response that contained the config key. Note also that I restarted Splunk after adding the config file and the README/myconfig.conf.spec. I'm not sure if that was required, but....&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 13:15:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91571#M1302</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-10-10T13:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: Manipulate conf file through Splunk/Rest API</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91572#M1303</link>
      <description>&lt;P&gt;Eventually it worked with curl also.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2013 16:52:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Manipulate-conf-file-through-Splunk-Rest-API/m-p/91572#M1303</guid>
      <dc:creator>klausJohan</dc:creator>
      <dc:date>2013-10-11T16:52:10Z</dc:date>
    </item>
  </channel>
</rss>

