feat(e2e): allow customizing genesis parameters on the manifest (backport #3969) #4310
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.
Closes #3961.
Similarly to #3967, introduces a new
genesis
field for manifest files. The format iskey = value
and multiple entries can be provided. For example,After the genesis document is produced by the
setup
implementation of the runner, the provided genesis customized configurations are applied to the generated genesis file. The solution also usesviper
, as it allows setting only some specific keys, leaving the pre-produced content untouched.Note: this PR is based atop #3964 for simplicity, but it does not need to.
PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code commentsThis is an automatic backport of pull request #3969 done by [Mergify](https://mergify.com).