Skip to content

deployment: extract l1 common config#14245

Open
nimrod-starkware wants to merge 1 commit into
05-28-deployment_extract_committer_common_configfrom
05-28-deployment_extract_l1_common_config
Open

deployment: extract l1 common config#14245
nimrod-starkware wants to merge 1 commit into
05-28-deployment_extract_committer_common_configfrom
05-28-deployment_extract_l1_common_config

Conversation

@nimrod-starkware
Copy link
Copy Markdown
Contributor

No description provided.

@reviewable-StarkWare
Copy link
Copy Markdown

This change is Reviewable

Copy link
Copy Markdown
Contributor Author

nimrod-starkware commented May 28, 2026

@cursor
Copy link
Copy Markdown

cursor Bot commented May 28, 2026

PR Summary

Low Risk
YAML-only refactor that relocates unchanged values; risk is limited to overlay merge/include mistakes affecting L1 service wiring per environment.

Overview
Extracts duplicated hybrid L1 sequencer overlay settings into a new shared file configs/overlays/hybrid/common/services/l1.yaml, following the same include pattern already used for services like committer and sierra-compiler.

mainnet, sepolia-alpha, and sepolia-integration l1.yaml overlays now pull in that common file and only define environment-specific base_layer_config (BPO block numbers and starknet_contract_address). Shared pieces moved to common include the replacer deployment configList, cross-service component host/port wiring, and the ClusterIP service port definitions.

Reviewed by Cursor Bugbot for commit 46ca1e9. Bugbot is set up for automated code reviews on this repo. Configure here.

@nimrod-starkware nimrod-starkware force-pushed the 05-28-deployment_extract_committer_common_config branch from 2893ae6 to 97735f4 Compare May 31, 2026 06:51
@nimrod-starkware nimrod-starkware force-pushed the 05-28-deployment_extract_l1_common_config branch from 81335aa to 46ca1e9 Compare May 31, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants