feat(network): durable eRPC config via erpc set|status|reset#772
Open
bussyjd wants to merge 3 commits into
Open
feat(network): durable eRPC config via erpc set|status|reset#772bussyjd wants to merge 3 commits into
bussyjd wants to merge 3 commits into
Conversation
Operators need multi-upstream eRPC baskets (scoring, rate-limit budgets, realtime eth_call cache) that helmfile/chart re-renders currently wipe. Mirror Hermes preserve-on-sync and recorded remotes: - Persist $CONFIG_DIR/rpc/erpc-overlay.yaml (0600) - Deep-merge networks/upstreams/rateLimiters/cache policies into live CM - ReconcileERPCOverlay after ReconcileRecordedRPCs on stack up - CLI: obol network overlay apply|status|clear|reconcile - Example HyperEVM basket + resume-order guard test Closes #763
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
|
What's the problem to be solved here? 'not having to edit a configmap' doesn't explain the root challenge
|
…terns Drop overlay apply/clear/reconcile. Operator surface is now the thin sell-info-shaped set/status/reset on `obol network erpc`, matching the intent: durable host-side eRPC config so local baskets survive stack up. Stack-up still calls ReconcileERPCOverlay internally (not a CLI verb).
bussyjd
changed the title
Drop len(a)+len(b) make capacities in mergeNetworksByID/mergeUpstreamsByID; grow on demand (same pattern as Hermes command_allowlist).
bussyjd
added a commit
that referenced
this pull request
Jul 16, 2026
… durable eRPC erpc set|status|reset
Contributor
Author
|
Merged into |
OisinKyne
approved these changes
Jul 16, 2026
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
3 participants
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
Prevents loss of local eRPC config on
obol stack up/ helm re-render by persisting operator eRPC fragments on the host and re-merging them after recorded remotes.Not a full ConfigMap replace: merge-by-id (networks / upstreams / budgets / cache policies).
CLI (aligned with stack verbs)
obol network erpc set -f <file.yaml>obol network erpc statusobol network erpc resetStack up still re-applies via internal
ReconcileERPCOverlay(not a public verb).Mirrors
sell info set|reset+ host-side records likerecorded-upstreams.yaml.Test plan
go test ./internal/network/ ./cmd/obol/obol network erpc --help→ set|status|reset/rpc/hyperevmstill worksCloses #763