• infos = Information about the blockresolver plugin is in keys below
• infos/author = Name name@.nosp@m.libe.nosp@m.lektr.nosp@m.a.or.nosp@m.g
• infos/licence = BSD
• infos/needs =
• infos/provides = resolver
• infos/recommends =
• infos/placements = rollback getresolver setresolver commit
• infos/status = maintained conformant compatible coverage specific unittest tested nodep libc configurable preview experimental difficult unfinished concept
• infos/metadata =
• infos/description =

The blockresolver can be used to only resolved a tagged block inside a configuration file.

Implementation details

blockresolver extracts the requested block from the configurations file and writes it into a temporary file. Afterwards Elektra will only work on the temporary file until kdbSet is called. On kdbSet the contents of the temporary file will be merged with parts outside of the requested block from the original file.

Usage

kdb mount -R blockresolver /path/to/my/file /mountpoint -c identifier="identifier-tag"

where identifier specifies the tag blockresolver will search for in the configuration file.

A block consists of 2 parts:

• beginning: the identifier suffixed with start
• end: the identifier suffixed with stop

Limitations

Currently the identifier must be unique.

Example

``` % cat /tmp/test.block bla bla bla

block config start

[section1] key1 = val1 [section2] key2 = val2

block config stop

asdf asdf asdf

% kdb mount -R blockresolver /tmp/test.block system/blocktest -c identifier="### block config" % kdb export system/blocktest [section1] key1 = val1 [section2] key2 = val2

% kdb set system/blocktest/section1/key12 val12 Create a new key system/blocktest/section1/key12 with string val12

% cat /tmp/test.block bla bla bla

block config start

[section1] key1 = val1 key12 = val12 [section2] key2 = val2

block config stop

asdf asdf asdf ```