$darkmode
Elektra 0.11.0
|
This release did not happen yet.
Please always update this file within every PR:
For example, Max would write:
Pick a random line to write your changes to minimize the chances of conflicts in this file.
For non-trivial changes, you can choose to be part of the highlighted changes. Please write a highlight section in this case.
After the horizontal line the release notes for the next version starts.
<<scripts/generate-news-entry
>>
We are proud to release Elektra <<VERSION>>.
Elektra serves as a universal and secure framework to access configuration settings in a global, hierarchical key database. For more information, visit https://libelektra.org.
You can also read the news on our website.
You can try out the latest Elektra release using our docker image elektra/elektra. This is the quickest way to get started with Elektra without compiling and other obstacles, simply run:
Elektra now comes with a powerful new feature that allows users to record and export changes made to the KDB: session recording. This feature enables you to easily track changes made to the configuration database over time, which helps troubleshoot issues, diagnose errors, and improve system performance. It even lets you undo the changes you've performed!
You can also export the changes as Ansible playbooks using the new Ansible storage plugin! This makes it easy to automate and reproduce system configurations. We think that this feature offers significant time savings and improved accuracy when managing complex systems.
Whether you're a system administrator, developer, or DevOps engineer, we believe that the session recording feature in Elektra will become an essential tool for managing and maintaining system configurations. Try it today and experience the benefits of streamlined configuration management.
Note: when you activate session recording, concurrency of Elektra will be somewhat limited. As long as it is active, a global lock will be created to ensure no two processes will write data simultaneously. This behavior is similar as to when multiple processes will write to the same configuration file. Applications should already handle this case gracefully, and just retry writing their configuration.
Based on the new and more versatile concept for backends, where backends are implemented as plugins, a new backend-plugin that uses ODBC data sources for storing keys has been developed. It was tested on Gentoo Linux with unixODBC using SQLite and PostgreSQL data sources. The ODBC backend-plugin can only be built if the ODBC library is available on the build system. This can be accomplished by installing e.g. unixODBC. Microsoft ODBC (on MS Windows) and iODBC should also be supported, but were not tested yet. If you use the plugin with another ODBC implementation as unixODBC, you are very welcome to update the documentation with your experiences!
The tutorial is a good place for getting started with the new ODBC backend for Elektra.
The following text lists news about the plugins we updated in this release.
ansible
plugin for exporting keysets as ansible-libelektra playbooks. _(Maximilian Irlinger @atmaxinger)_The text below summarizes updates to the C (and C++)-based libraries of Elektra.
elektraCopyError
function to copy error from one key to another _(Maximilian Irlinger @atmaxinger)_elektraCopyWarnings
function to copy warnings from one key to another _(Maximilian Irlinger @atmaxinger)_elektraCopyErrorAndWarnings
function to copy error and warnings from one key to another _(Maximilian Irlinger @atmaxinger)_elektraArrayGetPrefix
function. _(Maximilian Irlinger @atmaxinger)_Bindings allow you to utilize Elektra using various programming languages. This section keeps you up-to-date with the multi-language support provided by Elektra.
ElektraDiff
binding for C++ _(Maximilian Irlinger @atmaxinger)_dup
method of KeySet
now returns a wrapped object _(Maximilian Irlinger @atmaxinger)_KeySet::cut
that accepts a string for the keyname _(Maximilian Irlinger)_dup
method of Key
now returns a wrapped object _(Maximilian Irlinger @atmaxinger)_Key::isBelow
, Key::isBelowOrSame
and Key::isDirectBelow
that accept a string as the key name _(Maximilian Irlinger @atmaxinger)_cstdint
in key.hpp
. It is needed for an enum of type std::uint8_t
_(Florian Lindner @flo91)_ElektraDiff
binding _(Maximilian Irlinger @atmaxinger)___meta__
attribute on a key now returns a proper keyset _(Maximilian Irlinger @atmaxinger)_kdb.errors
to simplify extracting errors and warnings from keys _(Maximilian Irlinger @atmaxinger)_kdb.record
for interfacing with the session recording capabilities of Elektra _(Maximilian Irlinger @atmaxinger)_getConflictingKeys
method to kdb.merge.MergeResult
. _(Maximilian Irlinger @atmaxinger)_kdb mount
command will now automatically detect whether the given path is an absolute path. _(Maximilian Irlinger @atmaxinger)_smount
alias _(Hannes Laimer @hannes99)_const char * keyName (const Key * key)
which lead to failed building of the refman.pdf on recent TeX Live releases _(Florian Lindner @flo91)_succeed_if_keyset_contains_key_with_string
to assert that a certain key with a certain value must exist. _(Maximilian Irlinger @atmaxinger)_texlive-most
is no longer available, replaced it with other texlive packages. See https://archlinux.org/packages/?q=texlive _(Florian Lindner @flo91)_We are currently working on following topics:
We closed <> issues for this release.
<<scripts/git-release-stats <<VERSION>>.VER-1 <<VERSION>>
>>
Thanks to all authors for making this release possible!
We welcome new contributors! Read here about how to get started.
As first step, you could give us feedback about these release notes. Contact us via our issue tracker.
You can download the release from
The hashsums are:
<<scripts/generate-hashsums elektra-<<VERSION>>.tar.gz
>>
The release tarball is also available signed using GnuPG from
The following GPG Key was used to sign this release: 12CC44541E1B8AD9B66AFAD55262E7353324914A
Already built API documentation can be found
Subscribe to the RSS feed to always get the release notifications.
If you also want to participate, or for any questions and comments, please contact us via our issue tracker on GitHub.
For more information, see https://libelektra.org.
Best regards, Elektra Initiative