Ran
|
Files
49
|
Run time
4s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
Add 'rest-publish' command Supports: - Pushing multiple stanzas to a specific config endpoint at once, in a fairly efficient process. - Changes made on the server are show in the form of a diff. (Eventually, this should be configurable, and a dry-run mode should be added.) - Supports pushing to a live Splunk instance (via Splunkd REST API). This should replace the use of 'rest-export' for MOST use cases. - Supports reading and applying metadata (ACLs, owner, shared, app) to imported objects. - Any type of conf entry should be supported. Limitations: - **NO UNIT TESTING!** (This will require some fancy mock work.) - Doesn't support attribute-level metadata. - No SSL validation setup yet. This is primarily because of how Splunk's Python SDK works. For other Python HTTP libraries this is enabled by default. Squashed commit of the following: commit 80855edd0 Author: Lowell Alleman <lowell@kintyre.co> Date: Tue Feb 26 22:00:00 2019 -0500 Add changelog for rest-publish commit 8c8c60a98 Author: Lowell Alleman <lowell@kintyre.co> Date: Tue Feb 26 21:14:26 2019 -0500 Fixed small bug in rest-publish Resolved issue where 'diff' output would crash if the Splunkd version of the stanza contained a blank attribute (which was being returned as a None) which was screwing up the show_diff() function. - Replace values of None with '' for attributes returned from Splunkd (REST). This fixes the core issue in rest-publish. - Placed protective code in the show_diff() to be slightly better at handling unexpected None values. This is a secondary protection method that should at least NOT CRASH if somehow a None leaks in from somewhere else. commit 5ef130cfc Author: Lowell Alleman <lowell@kintyre.co> Date: Mon Feb 25 18:39:54 2019 -0500 Fixed bugs in rest-publish - Fixed issue where rest-publish w... (continued)
3415 of 3825 relevant lines covered (89.28%)
0.89 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|