apollo_deployments: expose jsonnet build() evaluator behind a testing feature#14686
Draft
nimrod-starkware wants to merge 1 commit into
Draft
Conversation
… feature Split the test-only jsonnet module into jsonnet_eval (the reusable build() evaluator) and jsonnet_tests (the parity/applicative helpers). Gate jsonnet_eval on any(feature = "testing", test) and make jrsonnet optional regular deps enabled by the new testing feature, so other crates (the integration-test harness) can call jsonnet_eval::build_service_configs without pulling jrsonnet into the default/production dependency graph. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 2, 2026
Open
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Split the test-only jsonnet module into jsonnet_eval (the reusable build()
evaluator) and jsonnet_tests (the parity/applicative helpers). Gate jsonnet_eval
on any(feature = "testing", test) and make jrsonnet optional regular deps enabled
by the new testing feature, so other crates (the integration-test harness) can
call jsonnet_eval::build_service_configs without pulling jrsonnet into the
default/production dependency graph.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com