Adds optional support for lmdb choice and sizing #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pr adds
dirsrv_use_mdbanddirsrv_mdb_max_size.Both those parameters modify the installation template only if explicitly set, as I think that the correct behaviour is to rely on the default values of the 389ds_base parameters that those options control. I.e. if the user does not have a choice, they should go with the default value of the distribution's 389ds_base, and not have a default value enforced by this role.
-- from https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html