Kintyre / ksconf / 526

87%

master: 90%

push

travis-ci

Make Splunk Packaging Great Again!

Created a context manager for conf file editing. Now you can write something
like this, and reading/update is handled automatically:

    with update_conf(path) as conf:
        conf["stanza"]["disabled"] = "true"

Many enhancements to the 'ksconf package' command:

- Implement blacklisting.  Added support for blacklist files (like .gitignore)
- Setting of app version and build.
- Overwrite app folder name, helpful when the source is '.'
- Implement 2 (out of 3) local handling options.  (Merge, the default is still
  not implemented, and no existing merge/combine logic will work here, because
  the destination is also a source.)
- Advanced build options:  (1) Creation of a "release" file which is written
  with the path to the created tarball, and (2) hook script/command integration
  for things like running "pip install" to download required 3rd party library
  during the build.
- Added some "magic" variable outputs for the app name.  So you can include
  the latest git HEAD ref, or extract the app.conf version, or name of the
  latest git tag, ... (Fully undocumented at the moment, but eventually it will
  be self describing).

It's becoming more obvious that I need a "SplunkApp" abstraction of some kind
to handle simple Splunk-like access to conf files collected within an app,
where reading things from default/local can be merged automatically upon read.
This could also include stanza updates, local->default merging, and some other
features I've added to package.py but should really be refactored elsewhere,
but I wanted to start by saving off a working version :=)  Ideally this
abstraction could be applied to tarball files too (allow for some reuse between
here and 'unarchive', for example.)

TL;DR:  'ksconf package' is less embarrassing now

208 of 208 new or added lines in 3 files covered. (100.0%)

4262 of 4906 relevant lines covered (86.87%)

7.74 hits per line