fix: stop honoring CODEX_MANAGED_CONFIG_PATH environment variable in production #8762
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.
Previously,
CODEX_MANAGED_CONFIG_PATHcould be used to override the path used to read managed config data,/etc/codex/managed_config.toml:codex/codex-rs/core/src/config_loader/layer_io.rs
Lines 97 to 100 in 771f1ca
While I believe this was designed to facilitate creating integration tests with test values of
managed_config.toml, this also meant that end-users could useCODEX_MANAGED_CONFIG_PATHto circumvent policies defined in/etc/codex/managed_config.toml, which was likely not the intention of the policy author.This PR plugs this loophole by:
managed_config_default_path()function to no longer honorCODEX_MANAGED_CONFIG_PATH.codex-app-serverstandalone binary to honor the environment variable, and only in debug builds.