apollo_deployments: jsonnet applicative config

[nimrod-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[nimrod-starkware]

• apollo_deployments: check applicative config matches deployed app_configs #14489 : 3 dependent PRs (#14480 , #14505 , #14606 )
• apollo_deployments: assemble and deserialize node config from jsonnet #14487
• apollo_deployments: assemble full node config via build.libsonnet #14486
• apollo_deployments: distributed layout jsonnet test #14485
• apollo_deployments: consolidated layout jsonnet test #14484
• apollo_deployments: test hybrid layout for infra config #14483
• apollo_deployments: introduce hybrid layout for infra config #14482
• apollo_deployments: introduce jsonnet building blocks for infra config #14481
• apollo_deployments: jsonnet applicative config #14479 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Medium Risk
Large declarative surface area for consensus, gateway validation, and batcher limits—incorrect defaults or missing overrides could misconfigure live deployments, though this is additive Jsonnet with no runtime code changes.

Overview
Introduces a centralized Jsonnet module that builds per-component Apollo applicative configs from an overrides object, mixing fixed deployment defaults with environment-specific values.

applicative_config.libsonnet documents the pattern: each field is either a concrete default or wired from overrides.* (chain/fee tokens, recorder URL, P2P multiaddrs, consensus committee/timeouts, gateway limits, state sync RPC ports, etc.). Shared knobs like validate_resource_bounds, revert behavior, and behavior_mode: 'starknet' are set once and reused across batcher, gateway, and mempool. State sync optional sub-configs use optionalStateSyncSubConfig to merge overrides into defaults or stay null when disabled.

Adds constants.libsonnet with DEFAULT_VALIDATION_ONLY (used for batcher validation_only via std.get).

Placeholder URLs remain for L1/oracle endpoints (e.g. Infura template, api.example.com); deployers must supply real overrides for production-sensitive fields.

^{Reviewed by Cursor Bugbot for commit 830827a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Versioned constants incomplete

Medium Severity

versioned_constants_overrides is wired only from overrides.versioned_constants_overrides, without embedding the fixed limits that used to live in general_config.json (invoke_tx_max_n_steps, max_recursion_depth, validate_max_n_steps, etc.). Only max_n_events is per-environment in KEYS_TO_BE_REPLACED, so sparse overrides can omit the other fields and change execution limits from the prior deployment defaults.

Additional Locations (2)

• crates/apollo_deployments/jsonnet/lib/applicative_config.libsonnet#L80-L81
• crates/apollo_deployments/jsonnet/lib/applicative_config.libsonnet#L381-L382

 

^{Reviewed by Cursor Bugbot for commit f93d240. Configure here.}

[cursor]

L1 oracle URLs hardcoded

Medium Severity

l1_gas_price_provider_config sets eth_to_strk_oracle_config.url_header_list and strk_to_usd_oracle_config.url_header_list to fixed https://api.example.com/api strings. Those endpoints were not in applicative app configs before; they came from deployment secrets. Baking in placeholder URLs can make gas-price oracles call the wrong host if secrets no longer override these fields in the new jsonnet flow.

 

^{Reviewed by Cursor Bugbot for commit f93d240. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f92f05c. Configure here.}