-
Notifications
You must be signed in to change notification settings - Fork 27
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
Symfony config parameters cannot be used in form configuration #99
Comments
Hello, |
Thanks for your reply. I can see what you are referring to. This does seem rather strange to me, as Bolt is based on Symfony, and yet has rolled it's own configuration reading instead of just using the default Symfony config system. As a consequence, I have to hard-code API keys into files instead of using environment variables or even the Symfony Secrets system. Bolt Forms could be a Symfony bundle, and have a standard bundle configuration file. I don't know the reasoning behind why this is not the case, but I'm guessing @bobdenotter will be able to shed some light on this. |
I encounter the same problem as you : I have 4 forms with ReCaptcha, and I have to centralize Google keys.
|
Aha that looks interesting (the config overrides) - thanks. I'll give that a try when I'm next back on that project. |
Bolt Forms 1.4.17
I'm using the reCaptcha v3 field type and need to specify the Google API keys. Currently it seems that you cannot use any Symfony configuration parameters or environment variables in this config file, like you can with Symfony YAML configuration, so I'm forced to hard-code the API keys, meaning they get stored in the Git repo and are visible to all.
Is this a known limitation?
Thanks
The text was updated successfully, but these errors were encountered: