Skip to content

deployment: extract common env to hybrid/common/common.yaml#14249

Open
nimrod-starkware wants to merge 1 commit into
05-28-deployment_extract_core_common_configfrom
05-28-deployment_extract_common_env_to_hybrid_common_common.yaml
Open

deployment: extract common env to hybrid/common/common.yaml#14249
nimrod-starkware wants to merge 1 commit into
05-28-deployment_extract_core_common_configfrom
05-28-deployment_extract_common_env_to_hybrid_common_common.yaml

Conversation

@nimrod-starkware
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Contributor Author

nimrod-starkware commented May 28, 2026

@reviewable-StarkWare
Copy link
Copy Markdown

This change is Reviewable

@cursor
Copy link
Copy Markdown

cursor Bot commented May 28, 2026

PR Summary

Low Risk
Config-only refactor with no application code changes; risk is limited to overlay merge/include behavior staying equivalent across environments.

Overview
Introduces a shared hybrid overlay at configs/overlays/hybrid/common/common.yaml and wires mainnet, sepolia-alpha, and sepolia-integration common.yaml files to pull it in via include.

The duplicated blocks removed from each network overlay are the image defaults (repository/pull policy), shared sequencerConfig fee tokens and versioned-constants overrides, monitoring service port 8082, health probes, GCP pod monitoring, and RUST_ env vars. Each environment file now only keeps network-specific pieces such as image tag, chain_id, whitelist, and feeder/recorder URLs.

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

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