8000 feat(e2e): allow customizing genesis parameters on the manifest (backport #3969) by mergify[bot] · Pull Request #4310 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat(e2e): allow customizing genesis parameters on the manifest (backport #3969) #4310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor
@mergify mergify bot commented Oct 20, 2024

Closes #3961.

Similarly to #3967, introduces a new genesis field for manifest files. The format is key = value and multiple entries can be provided. For example,

genesis = [ 
    "consensus_params.evidence.max_bytes = 1000", 
    "chain_id = pr3969" 
]

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 uses viper, 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

  • Tests written/updated
  • Changelog entry added in .changelog (we use unclog to manage our changelog)
  • Updated relevant documentation (docs/ or spec/) and code comments

This is an automatic backport of pull request #3969 done by [Mergify](https://mergify.com).

Closes #3961.

Similarly to #3967, introduces a new `genesis` field for manifest files.
The format is `key = value` and multiple entries can be provided. For
example,

```
genesis = [
    "consensus_params.evidence.max_bytes = 1000",
    "chain_id = pr3969"
]
```

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 uses `viper`, 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

- [ ] Tests written/updated
- [ ] Changelog entry added in `.changelog` (we use
[unclog](https://github.com/informalsystems/unclog) to manage our
changelog)
- [ ] Updated relevant documentation (`docs/` or `spec/`) and code
comments

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Andy Nogueira <me@andynogueira.dev>
(cherry picked from commit 6c5cd32)

# Conflicts:
#	test/e2e/pkg/manifest.go
#	test/e2e/pkg/testnet.go
#	test/e2e/runner/setup.go
@mergify mergify bot requested a review from a team as a code owner October 20, 2024 08:40
@mergify mergify bot added the conflicts label Oct 20, 2024
@mergify mergify bot requested a review from a team as a code owner October 20, 2024 08:40
@mergify mergify bot assigned cason Oct 20, 2024
Copy link
Contributor Author
mergify bot commented Oct 20, 2024

Cherry-pick of 6c5cd32 has failed:

On branch mergify/bp/v1.x/pr-3969
Your branch is up to date with 'origin/v1.x'.

You are currently cherry-picking commit 6c5cd3292.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .golangci.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   test/e2e/pkg/manifest.go
	both modified:   test/e2e/pkg/testnet.go
	both modified:   test/e2e/runner/setup.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@cason cason changed the base branch from v1.x to mergify/bp/v1.x/pr-3967 October 20, 2024 09:10
@cason cason closed this Oct 20, 2024
@zrbecker zrbecker deleted the mergify/bp/v1.x/pr-3969 branch February 7, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0