refactor(common): allow custom default configs #6068
Merged
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.
Description
Adds
load_configuration_with_overrides
that exposes the functionality to load configs without including the prompting and compiled in config templates.Motivation and Context
On the tari-dan repo, we want to customize the default configurations without having to PR to the tari repo. L2-related configs can be managed in the tari-dan repo and can be removed from this repo in a subsequent PR.
How Has This Been Tested?
Manually by starting a new base node and checking the config.toml
What process can a PR reviewer use to test or verify this change?
Base node default config works as before
Breaking Changes