Thanks for covering this. You should have spent some more time on springboot relaxed binding where it can automatically map your env variables with properties based on certain rules like replace underscore with dot, delete all hyphens and lowercase to uppercase.
Thank you Dan for the video! How can a Spring Boot 3 application handle secrets like database passwords and API keys that need frequent rotation due to expiration? Using a key vault helps with security, but it doesn’t solve the issue of updating secrets in a running application without downtime. Is there a reliable way to dynamically refresh secrets at runtime without relying on cron jobs or fetching secrets only during deployment? Can you please create a video about properly handling secrets inside your spring boot 3 application.
About security should I be concerned about that the environment variable could be discovered if you check the list of running process or even declared as environment variable? Another point: And what about application profiles configuration, settings as environment variable for different environments (dev/production) should be considered better than profiles?
Having an environment variable named "APP_API_KEY" is enough, you do NOT have to write something like "app.api.key=${MY_API_KEY}". See "Externalized Configuration" > "Binding From Environment Variables" in Spring Boot documentation.
Short and useful. That’s what I need every end of the day to learn a little piece, to become better 🎉
Thanks for covering this. You should have spent some more time on springboot relaxed binding where it can automatically map your env variables with properties based on certain rules like replace underscore with dot, delete all hyphens and lowercase to uppercase.
came here to give my like!
Tks... Congrats from Brazil.
Hi Dan. can you please add a playlist on microservices covering several design patterns
Grate! as always!
Thank you Dan for the video!
How can a Spring Boot 3 application handle secrets like database passwords and API keys that need frequent rotation due to expiration? Using a key vault helps with security, but it doesn’t solve the issue of updating secrets in a running application without downtime. Is there a reliable way to dynamically refresh secrets at runtime without relying on cron jobs or fetching secrets only during deployment? Can you please create a video about properly handling secrets inside your spring boot 3 application.
Make Java Great Again 2024
goods video!!!!! useful great
About security should I be concerned about that the environment variable could be discovered if you check the list of running process or even declared as environment variable?
Another point: And what about application profiles configuration, settings as environment variable for different environments (dev/production) should be considered better than profiles?
I believe Spring Cloud Config would be a better option for such cases.
Having an environment variable named "APP_API_KEY" is enough, you do NOT have to write something like "app.api.key=${MY_API_KEY}".
See "Externalized Configuration" > "Binding From Environment Variables" in Spring Boot documentation.
@@vrvr82 I mentioned that but I thought showing it off this way might make it a little more explicit and click 🤷♂️
can i develop Ai teacher or AI recuriter if i watch and learn your videos
All is well until it goes to production that's what I need to focus on
I do not even go to spring initializer. I generate the project directly from inside Intelij.
How can I do this in VS Code?