NotificationsYou must be signed in to change notification settings
Fork9.8k
Star30.9k

[FrameworkBundle] Make`ConfigDebugCommand` use its container to resolve env vars#62681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Open

MatTheCat wants to merge1 commit intosymfony:6.4

base:6.4

Choose a base branch

fromMatTheCat:ticket_62554

Open

[FrameworkBundle] Make`ConfigDebugCommand` use its container to resolve env vars#62681

MatTheCat wants to merge1 commit intosymfony:6.4fromMatTheCat:ticket_62554

Conversation

Copy link

Contributor

MatTheCat commentedDec 7, 2025•
edited
Loading

Q	A
Branch?	6.4
Bug fix?	yes
New feature?	no
Deprecations?	yes
Issues	Fix#62554
License	MIT

TheConfigDebugCommand currently cannot use theSodiumVault to load env vars because its$secretsDir depends on one, so calling it with--resolve-env-vars fails if an env var is only present in the vault. I’m not sure if it’s for the same reason but compiling the container with$resolveEnvPlaceholders suffers from the same issue.

I didn’t find a way to fix this so this PR works around it by setting the new container’s env var processors as the command’s so that the vault (and anything that could be used to resolve env vars) is correctly initialized.