Ksconf

Latest version: v0.13.9

Safety actively analyzes 688803 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 12

0.12.2

~~~~~~~~~~~~~~~~~~~~~~~~~~~

* *App building with Ksconf*: Added a convenience method to allow running ksconf commands more easily during the build process.
You can now invoke ksconf using :py:meth:`~ksconf.build.BuildStep.run_ksconf` method which allows direct execution of a ksconf command.
Previously this was accomplished by using :py:meth:`~ksconf.build.BuildStep.run`, using Python interpreter internal path as the executable, launching the ksconf in "module" mode.
So this approach is simpler and in the future it may be invoked internally, removing the need for launching an additional Python process.
* Enhanced plugin error handling.
* Many little doc build fixes.

0.12.1

~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Introducing :ref:`ksconf_cmd_attr-get` and :ref:`ksconf_cmd_attr-set` - the newest and simplest ksconf commands ever!
Use this to quickly grab and/or update a specific stanzas, attribute combination from a conf file.
* Add new attribute-level matching logic to ``ksconf filter``.
Use ``--attr-matches`` and/or ``--attr-not-matches`` to match specific attribute and value combinations for stanza matching.
This can be used to find props with a specific ``KV_MODE``, find saved search containing a specific search command, or list indexes not using ``volume:`` designation.
See the :ref:`ksconf_cmd_filter` docs for example usage.
Thanks to yohonet for inspiring this change, along with the new ``attr-get`` command.
* Add ``--in-place`` processing behavior for :ref:`ksconf_cmd_merge` to simplify the process of merging new content into an existing conf file.
* Docs Improvements:
* Fixed documentation generation bug that prevented command line options from showing up in the per-command doc pages. (Broken since v0.10)
* Fixed docs embedded in the Splunk app (and possibly causing some other display issues on the main rtd site)
* Fixed some CLI file handling bug that resulted in broken use of ``-`` (stdin) and/or fancy shell commands involving ``<(some command)`` syntax, which can be a helpful trick to reduce the number of temporary files.

0.12

-----------

**Highlights:**

* Add new ksconf subcommands for very basic, but previously missing, :ref:`ksconf_cmd_attr-get` and :ref:`ksconf_cmd_attr-set`.
These commands allow for easy target information for capture or update.
* Pre-commit hooks have been moved into their own `ksconf-pre-commit repo`.
To allow time for migration to the new repo, the existing hooks will remain for a few release before being removed.
To migrate, simply add ``-pre-commit`` to the end of the ``repo`` field, and update ``rev`` to ``v0.12.0`` or later.


**Packaging changes:**

* Dropped hard ``lxml`` from requirements.
This is still handled automatically when using the pre-commit hooks (from the new repository).
But this may be missing.
To get access to all CLI functionality, run ``pip install ksconf[thirdparty]``,
or for the full experience use ``pip install ksconf[fully-loaded]``
* Remove the use of the ``endpoints`` python package and shift to using ``importlib.metadata`` (or the equivalent backport), as it suggested by the original author of that package.
The original necessity of this library was to workaround performance issues in ``pkg_resources`` (and the fact that it's no present in Splunk's embedded python.
This move reduces code complexity but it does mean some additional runtime dependencies on older versions of Python.
In many cases, this really isn't a new dependency, since pluggy requires it as well.

0.12.0

~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Drop ``lxml`` and ``endpoints`` dependencies.
* Moved pre-commit hooks to `ksconf-pre-commit repo`_, and started deprecation of the hooks in the main `ksconf repo`_.

0.11.9

~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Splunk app packaging changes only. No need to update the package for CLI usage.
* Fix packaging bug impacting the Ksconf Splunk app. This issue was introduced in v0.11.6.
Thanks to yohonet for brining this to my attention.
* Note that this took two release cycles to fully resolve. (Ignore ksconf v0.11.8)

0.11.7

~~~~~~~~~~~~~~~~~~~~~~~~~~~

* Support disabling of plugins by name via ``KSCONF_PLUGIN_DISABLE`` environment variable. This expects a space separated lists of plugin names.
* Add new plugins documentation.

Page 3 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.