-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DependencyInjection] Add urlencode
function to EnvVarProcessor
#52369
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea. I've already had a project that crashed because a &
slipped into an automatically generated password.
src/Symfony/Component/DependencyInjection/Tests/EnvVarProcessorTest.php
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM.
We are feature freeze in preparation of 6.4 and 7.0. This will be for version 7.1.
urlencode
function to EnvVarProcessor
aab25b5
to
1439858
Compare
Thank you @crtl. |
This PR adds
urlencode
to the defaultEnvVarProcessor
to allow encoding environment variables in config files.The comes handy when environment variables are provided by the OS and not through .env because those values are often not compatible with DSN syntax for doctrine or mailer components.
In my case our app was deployed on an AWS stack and environment variables for SMPT and database where automatically provided in the deployment process and replaced in the respective .env files.
Because those values where not encoded they would cause issues with DSN format requireing me to commit them in my
.env.prod
which circumvents the purpose of the whole system.Usage: