You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Disabled urllib3 warnings
- Added timeout=0 on `SplunkVersionControl ChangeDetector Directory` savedsearch
- Added some minor comments about `/services/properties/savedsearches/default` (no changes in this version)
- Updated various internal calls to use sslVerify setting. Hopefully nothing will break but this will result in more SSL verification in various parts of the code
Library updates:
- Updated Splunk python SDK to 1.7.3
## How does this compare with other version control apps for Splunk?
318
+
As of October 2022, there are still no signs of version control within the Splunk Enterprise (or cloud) product, however you do have a few options in terms of a version control app, these include:
319
+
-[Git Version Control for Splunk](https://splunkbase.splunk.com/app/4182) - this app provides a modular input to help with getting configuration into a git repository from the filesystem. Note: on-prem instances only, no Splunk Cloud support.
320
+
-[FN1315 - Cover Your Assets: Protect Your Knowledge Objects from Yourself (and Others) - A Paychex story github](https://github.com/paychex/Splunk.Conf19) - this git location provides a list of searches that produce curl commands you can use to restore objects. This can work on-prem or in Splunk Cloud
321
+
-[Splunk2Git](https://github.com/paychex/splunk-python/tree/main/Splunk2Git) - Paychex's script to move Splunk knowledge objects into git using REST API
322
+
-[Version Control for Splunk (this app)](https://splunkbase.splunk.com/app/4355) - this app uses the REST API to download configuration and store inside a git repository in JSON format. Supports restoration of objects via dashboard (no admin support required). This can work on-prem or on Splunk Cloud remotely (this app runs on prem)
323
+
-[VersionControl for SplunkCloud](https://splunkbase.splunk.com/app/5061) - these are the dashboards and savedsearches that are installed on the SplunkCloud instance to support the version control app running remotely
324
+
-[Search Head Backup](https://splunkbase.splunk.com/app/6438) - backup to an index, works in Splunk Cloud
325
+
317
326
## Release Notes
327
+
### 1.2.10
328
+
Updates:
329
+
- Disabled urllib3 warnings
330
+
- Added timeout=0 on `SplunkVersionControl ChangeDetector Directory` savedsearch
331
+
- Added some minor comments about `/services/properties/savedsearches/default` (no changes in this version)
332
+
- Updated various internal calls to use sslVerify setting. Hopefully nothing will break but this will result in more SSL verification in various parts of the code
333
+
334
+
Library updates:
335
+
- Updated Splunk python SDK to 1.7.3
336
+
318
337
### 1.2.9
319
338
New features:
320
339
- Added wildcard support for restores, so restore a savedsearch of `Test*` will now restore any savedsearch starting with Test, wildcards can be used on any knowledge object
# optimisation to deal with the giant display.visualizations... on savedsearches only
239
+
# an improved version of this optimisation may be to use /services/properties/savedsearches/default and to filter out *all* default parameters for searches
#REST API does not support the creation of null queue entries as tested in 7.0.5 and 7.2.1, these are also unused on search heads anyway so ignoring these with a warning
381
+
# REST API does not support the creation of null queue entries as tested in 7.0.5 and 7.2.1, these are also unused on search heads anyway so ignoring these with a warning
382
+
# however this might instead work on /services/properties/... or /services/configs/conf-... endpoints, to be tested if the requirement comes up
logger.info("i=\"%s\" Dropping the backup of name=\"%s\" of type=%s in app context app=%s with owner=%s because nullQueue entries cannot be created via REST API (and they are not required in search heads)"% (self.stanzaName, info["name"], type, app, info["owner"]))
0 commit comments