-
Notifications
You must be signed in to change notification settings - Fork 85
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
feat: allow to override ORM connection properties #7816
Comments
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Here is example to override java variables:
env variables
|
Hi @yurem I am updating documents for these changes. I have a quick question: The steps above will change the property value only for |
@ossdhaval its actually the opposite in VM. If you pass that env globally it will change for all the modules. |
right, it depends on scope where you export env properties. Global properties will be used in all jans app. If you need to export them for specific app you can use |
ORM should use environment/java variables with same names to override ORM configuration properties.
Also it should use environment variables like
CONNECTION_URI
to override properties likeconnection.uri
andconnection-uri
The text was updated successfully, but these errors were encountered: