feat: set-genesis-peers task and assembler peers.json upload#43
Merged
feat: set-genesis-peers task and assembler peers.json upload#43
Conversation
The genesis assembler now downloads each node identity from S3 after assembling genesis.json and builds a peers.json containing full Tendermint peer addresses using in-cluster DNS. A new set-genesis-peers sidecar task downloads this file, filters out the current node using its local node_key.json, and writes persistent_peers to config.toml. This replaces the discover-peers step in the genesis ceremony plan, which was failing because genesis ceremony nodes have no external peer sources configured.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
set-genesis-peerssidecar task downloads peers.json, filters out the current node using its local node_key.json, and writes persistent_peers to config.tomlnamespaceas a required parameter to the assembler for constructing DNS addressesContext
Genesis ceremony nodes were failing at the
discover-peersstep because there are no external peer sources (EC2 tags, static) configured — all nodes start simultaneously in the same cluster. This produces the peer list as a ceremony artifact instead, matching the pattern from the legacy SeiNodePool approach.Companion controller PR needed to wire
namespaceinto assembler params and replacediscover-peerswithset-genesis-peersin the genesis plan.Test plan