<?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: Source Control Management in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368341#M5259</link>
    <description>&lt;P&gt;@DalJeanis: which of the following was your intent:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;create the changes within a live instance of Splunk and then log those changes in source control&lt;/LI&gt;
&lt;LI&gt;making the changes directly in a source-code repository and then deploy the changes out to your Splunk installs&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Mon, 08 May 2017 20:13:53 GMT</pubDate>
    <dc:creator>LukeMurphey</dc:creator>
    <dc:date>2017-05-08T20:13:53Z</dc:date>
    <item>
      <title>Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368339#M5257</link>
      <description>&lt;P&gt;The more that I understand and rely only the tooling that I can create in Splunk: &lt;BR /&gt;
- saved searches&lt;BR /&gt;
- alerts&lt;BR /&gt;
- reports&lt;BR /&gt;
- dashboards&lt;BR /&gt;
- Field knowledge Objects&lt;BR /&gt;
- Lookup table definitions&lt;/P&gt;

&lt;P&gt;The more that I realize that I will ultimately need some notion of source code management for the objects that I create.  I want to protect myself from me or my teammates accidentally changing the tooling that we are coming to count on.&lt;/P&gt;

&lt;P&gt;Are there any Source Control Management tools that work (and better yet, integrate) well with Splunk?  Does anyone have any experience that they could share?&lt;/P&gt;

&lt;P&gt;I am currently on a path to just paste a copy of the things that my team counts on into Accurev (the tool our AD team uses), but it would be better to have integration to &lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;automatically populate the SCM tool&lt;/LI&gt;
&lt;LI&gt;Deploy those things to Splunk as a shared object, ideally such that they run under some system type ID (rather than my ID, as the creator)&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 08 May 2017 17:32:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368339#M5257</guid>
      <dc:creator>MonkeyK</dc:creator>
      <dc:date>2017-05-08T17:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368340#M5258</link>
      <description>&lt;P&gt;The most common one is git, in particular Atlassian's Bit Bucket Server (formerly Stash).  Here's a link to one discussion, but there are at least 4-5 threads on various issues and questions.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/312571/best-way-to-use-git-for-source-version-control-wit.html"&gt;https://answers.splunk.com/answers/312571/best-way-to-use-git-for-source-version-control-wit.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 19:17:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368340#M5258</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-05-08T19:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368341#M5259</link>
      <description>&lt;P&gt;@DalJeanis: which of the following was your intent:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;create the changes within a live instance of Splunk and then log those changes in source control&lt;/LI&gt;
&lt;LI&gt;making the changes directly in a source-code repository and then deploy the changes out to your Splunk installs&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 08 May 2017 20:13:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368341#M5259</guid>
      <dc:creator>LukeMurphey</dc:creator>
      <dc:date>2017-05-08T20:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368342#M5260</link>
      <description>&lt;P&gt;Sorry, my initial search must have been way off.  Thanks for pointing me in the right direction.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 22:23:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368342#M5260</guid>
      <dc:creator>MonkeyK</dc:creator>
      <dc:date>2017-05-08T22:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368343#M5261</link>
      <description>&lt;P&gt;You may also be interested in &lt;A href="https://answers.splunk.com/answers/484716/is-anyone-using-cicd-to-deploy-splunk-apps.html"&gt;https://answers.splunk.com/answers/484716/is-anyone-using-cicd-to-deploy-splunk-apps.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 22:35:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/368343#M5261</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2017-05-09T22:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: Source Control Management</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/643591#M9470</link>
      <description>&lt;P&gt;You might like &lt;A href="https://splunkbase.splunk.com/app/6895" target="_blank"&gt;https://splunkbase.splunk.com/app/6895&lt;/A&gt; to track changes to your knowledge objects. It's no effort, doesn't require git or anything else, and works equally well on-prem and in cloud.&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 09:53:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Source-Control-Management/m-p/643591#M9470</guid>
      <dc:creator>gabriel_vasseur</dc:creator>
      <dc:date>2023-05-17T09:53:37Z</dc:date>
    </item>
  </channel>
</rss>

