Skip to content

apollo_deployments: retire dead preset/replacer generation machinery#14647

Draft
nimrod-starkware wants to merge 1 commit into
nimrod/jsonnet/retire-preset-config-pathfrom
nimrod/jsonnet/retire-replacer-generation
Draft

apollo_deployments: retire dead preset/replacer generation machinery#14647
nimrod-starkware wants to merge 1 commit into
nimrod/jsonnet/retire-preset-config-pathfrom
nimrod/jsonnet/retire-replacer-generation

Conversation

@nimrod-starkware

Copy link
Copy Markdown
Contributor

Runtime (Phase 1) and the cdk8s deploy (Phase 2) now load only native config, so
the preset-replacer GENERATION machinery is dead. Remove it:

  • Delete resources/app_configs/replacer_*.json (19 files), src/replacers.rs, and the
    deployment_generator bin (+ its [[bin]] entry and the tempfile dev-dep).
  • service.rs: drop the replacer-annotation plumbing, the deploy-path config_to_preset/
    prune_by_is_none calls, and the orphaned ComponentConfigsSerializationWrapper. Keep
    KEYS_TO_BE_REPLACED (still feeds the retained applicative_matches_app_configs guard's
    exclusion set).
  • Delete the 3 migration guard tests (deployment_files_are_up_to_date,
    replacer_config_entries_are_in_config, duplicate_config_entries). Keep the
    build_*_deserializes, applicative_matches_app_configs, and *_infra_matches_rust guards,
    and get_component_configs.

The cdk8s configList field is presence-checked only (its targets live in a different
directory and are not read under native), so deleting the base replacer JSONs leaves
synth green. apollo_deployments: 9 tests pass; cdk8s synth green for all overlays.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

@reviewable-StarkWare

Copy link
Copy Markdown

This change is Reviewable

nimrod-starkware commented Jun 28, 2026

Copy link
Copy Markdown
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

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

@nimrod-starkware nimrod-starkware force-pushed the nimrod/jsonnet/retire-replacer-generation branch from 89ab258 to c0351e0 Compare June 28, 2026 10:14
@nimrod-starkware nimrod-starkware force-pushed the nimrod/jsonnet/retire-preset-config-path branch from 0df4a4a to a07b98f Compare June 28, 2026 10:14
@nimrod-starkware nimrod-starkware force-pushed the nimrod/jsonnet/retire-preset-config-path branch from a07b98f to a3d7879 Compare June 28, 2026 10:30
@nimrod-starkware nimrod-starkware force-pushed the nimrod/jsonnet/retire-replacer-generation branch from c0351e0 to 4f5f772 Compare June 28, 2026 10:30
Runtime (Phase 1) and the cdk8s deploy (Phase 2) now load only native config, so
the preset-replacer GENERATION machinery is dead. Remove it:
- Delete resources/app_configs/replacer_*.json (19 files), src/replacers.rs, and the
  deployment_generator bin (+ its [[bin]] entry and the tempfile dev-dep).
- service.rs: drop the replacer-annotation plumbing, the deploy-path config_to_preset/
  prune_by_is_none calls, and the orphaned ComponentConfigsSerializationWrapper. Keep
  KEYS_TO_BE_REPLACED (still feeds the retained applicative_matches_app_configs guard's
  exclusion set).
- Delete the 3 migration guard tests (deployment_files_are_up_to_date,
  replacer_config_entries_are_in_config, duplicate_config_entries). Keep the
  build_*_deserializes, applicative_matches_app_configs, and *_infra_matches_rust guards,
  and get_component_configs.

The cdk8s configList field is presence-checked only (its targets live in a different
directory and are not read under native), so deleting the base replacer JSONs leaves
synth green. apollo_deployments: 9 tests pass; cdk8s synth green for all overlays.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@nimrod-starkware nimrod-starkware force-pushed the nimrod/jsonnet/retire-replacer-generation branch from 4f5f772 to ece79f9 Compare June 28, 2026 14:04
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