import strategy
Opened this issue · 2 comments
It isn't clearly documented what happens with previous keys and there should also be several import strategies available.
Should we support the same import strategies as the kdb import tool? If so, we should put the merger into its own library and expose it through the python library.
Should we support the same import strategies as the kdb import tool?
We should use the same import strategies in all the tooling (and also everywhere else via API). Which strategies these should be, would be a task to find out within your use cases. The ones described in doc/help/elektra-merge-strategy.md are the ones which were needed up to now. "unchanged" should be stabilized, "import" can be removed.
If so, we should put the merger into its own library
It is in its own library! In the Elektra repo, src/libs/merge produces the lib libelektra-merge.
and expose it through the python library.
Yes, that would be amazing. Also the mounting should be exposed via the Python library. There is already ElektraInitiative/libelektra#323 but this will need to be redone after @flo91 made his library in C.