deployment,ci: add hybrid native override layers and their validation tests#14610
Conversation
9e2747d to
88fff14
Compare
ce5cb7e to
1c01342
Compare
88fff14 to
8e7c47b
Compare
1c01342 to
5eb0fdd
Compare
nimrod-starkware
left a comment
There was a problem hiding this comment.
split to two separate PR's
@nimrod-starkware made 2 comments.
Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion.
.github/workflows/sequencer_cdk8s-test.yml line 74 at r2 (raw file):
echo "Installing pip dependencies..." pipenv install echo "Running pytest suite..."
this change should be in prev PR
Code quote:
echo "Running pytest suite..."
nimrod-starkware
left a comment
There was a problem hiding this comment.
@nimrod-starkware resolved 1 discussion.
Reviewable status: 0 of 4 files reviewed, all discussions resolved.
8e7c47b to
1a279e2
Compare
5eb0fdd to
099442e
Compare
1a279e2 to
5950d10
Compare
099442e to
635f6e5
Compare
635f6e5 to
bdaadc1
Compare
5950d10 to
5ed6bbd
Compare
…ckstep test Add the sepolia-integration env sequencer_config.jsonnet override layer consumed by the native config builder, plus its per-layer lockstep test: the layer's jsonnet, flattened to dotted keys, must exactly match the combined config.sequencerConfig of the sepolia-integration YAMLs (with #is_none folded and components.* dropped), keeping the native and preset generation paths from drifting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview Extends the native config lockstep regression from the common layer only to every overlay layer: docs/comments now describe per-layer parity, and Reviewed by Cursor Bugbot for commit 0034285. Bugbot is set up for automated code reviews on this repo. Configure here. |
bdaadc1 to
0034285
Compare
5ed6bbd to
03b48d4
Compare

Add the base (common) and sepolia-integration sequencer_config.jsonnet override
layers consumed by the native config builder, plus the tests that validate them:
the AUTHORITATIVE PARITY test (native build vs folded/filtered preset across
hundreds of applicative keys) with its negative gate, the "jsonnet mirrors combined
YAML" layer tests, and the cross-repo overlay collision / disjoint-leaf-key guards.
The devops-dependent tests skip cleanly when the devops overlay checkout is absent
(as in CI). Run the full test/ pytest suite in the cdk8s CI workflow instead of
only the port-uniqueness test, so these gate in CI.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com