Markus Raab
Markus Raab
As brought up by @kodebach in #4415 we actually misuse cascading keys to do something else for cascading mountpoints. Cascading keys should have the semantics to search in one namespace...
kdb set: always do cascading set (for validation) ## Current behavior `kdb set user:/test value` does not validate. ## Expected behavior `kdb set user:/test value` should validate (except if `-f`...
This issue gives up-to-date information about the health of our build system. Report here any permanent problems (that cannot be fixed by rerunning the build job). Temporary problems should be...
getopt reorders the arguments which causes a problem when commands are nested. E.g. `bin/kdb elektrify-getenv echo -n -e "hello world"` Causes `The command elektrify-getenv is not known` (even though the...
Not every command only uses return codes from 10 and up. - [ ] kdb-plugin-check.md - [ ] kdb-plugin-info.md - [ ] kdb-meta-get.md - [ ] kdb-meta.show.md - [ ]...
As @dev2718 found out, it is best to disable cascading writes with an exception if the namespace is explicitly given. So disable cascading writes in: - [x] `kdb set` (in...
Currently we have a few aliases, e.g. smount for spec-mount. I propose to remove these aliases, as their benefit is minor, they can be confusing and the man pages do...
From #4012: > It should work like git (same as commands in elektraGetOpts). If we are interested in making it work like git, we need a patch to use elektraGetOpts...
## Steps to Reproduce the Problem ```sh kdb meta-set "spec:/sw/redshift/#0/current/mode" default continual kdb set "/sw/redshift/#0/current/mode" print kdb get "/sw/redshift/#0/current/mode" ``` ## Expected Result That the second command fails because the...
The `kdbGet` optimization to do nothing if everything is unchanged seems to have a bug: If we remove the config file, the resolver will return 0. In the case of...