![Environment Specific Application. Properties File in Spring Boot Application [Closed]](https://docuprint.cloud68.co/uploads/environment-specific-application-properties-file-in-spring_1200.jpg)
In my Spring Boot application, i want to create environment specific properties file. The packaging type of my application in war and i am executing it in embedded tomcat. I use sts and execute the main from sts itself.
- Can i have environment specific properties file like application-${env-value}.properties?
In above case, env-value will have values as local/devl/test/prod
Where to set the env-value file? For local, i can set it as the jvm argument through sts
Who reads the application.properties in Spring Boot application.
How to load the environment specific properties file? For ex - if i set the database uid,pwd, schema etc in environment specific property file, in that case will the datasource be able to understand the properties in it?
Can i use application.properties and application-local.properties file at same time?
4 Answers
Spring Boot already has support for profile based properties.
Simply add an application-[profile].properties file and specify the profiles to use using the spring.profiles.active property.
-Dspring.profiles.active=local
This will load the application.properties and the application-local.properties with the latter overriding properties from the first.
Yes you can. Since you are using spring, check out @PropertySource anotation.
Anotate your configuration with
@PropertySource("application-${spring.profiles.active}.properties")
You can call it what ever you like, and add inn multiple property files if you like too. Can be nice if you have more sets and/or defaults that belongs to all environments (can be written with @PropertySource{...,...,...} as well).
@PropertySources({
@PropertySource("application-${spring.profiles.active}.properties"),
@PropertySource("my-special-${spring.profiles.active}.properties"),
@PropertySource("overridden.properties")})
Then you can start the application with environment
-Dspring.active.profiles=test
In this example, name will be replaced with application-test-properties and so on.
we can do like this:
in application.yml:
spring:
profiles:
active: test //modify here to switch between environments
include: application-${spring.profiles.active}.yml
in application-test.yml:
server:
port: 5000
and in application-local.yml:
server:
address: 0.0.0.0
port: 8080
then spring boot will start our app as we wish to.
My Point , IN this arent way asking developer to create all environment related in single go, resulting in risk of exposing Production Configuration to end developer
as per 12-Factor, shouldnt be enviornment specific reside in Enviornment only .
How do we do for CI CD
- Build Spring one time and promote to aother environment, in that case, if we have spring jar has all environment, it iwll security risk, having all environment variable in GIT
