deploy: add support for cometbft postgres indexing #3228
Merged
Conversation
This file contains 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
The penumbra-node chart now has opt-in support for storing CometBFT events in a postgres sidecar. See relevant docs at [0]. The sole downstream use case for this work to date is cuiloa [1], a block explorer for Penumbra. There are some shortcuts in this logic, mostly related to hardcoding db connection info, but the db is intra-cluster cluster only, so the risk is minimal. Prioritizing developer velocity right now. [0] https://docs.cometbft.com/v0.37/app-dev/indexing-transactions#postgresql [1] https://github.com/ejmg/cuiloa
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.
The penumbra-node chart now has opt-in support for storing CometBFT events in a postgres sidecar. See relevant docs at [0]. The sole downstream use case for this work to date is cuiloa [1], a block explorer for Penumbra. There are some shortcuts in this logic, mostly related to hardcoding db connection info, but the db is intra-cluster cluster only, so the risk is minimal. Prioritizing developer velocity right now.
[0] https://docs.cometbft.com/v0.37/app-dev/indexing-transactions#postgresql
[1] https://github.com/ejmg/cuiloa