Spring Boot – How Do You Externalize Application Properties

Sitewide-Feb4of4300x250 Application properties, e.g. the database connection parameters, shouldn’t be hard-coded in our applications. They should instead be put externally, say in properties/YML files, and injected into the application.

Spring Boot has multiple ways to handle this. It’s detailed in the reference material, but me share some key steps that I follow.

1) Place all the properties (or .yml) files in /src/main/resources/config folder

Spring Boot, by default, looks for properties files either in classpath root, i.e. /src/main/resources, or inside a config sub-folder. I personally prefer the config sub-folder.

2) Use Spring profiles to segregate properties

Some of the application properties would be same across environments, while some would vary. For example, multipart.enabled=false could be same across all environments, whereas spring.datasource.url could vary on development, test and production environments.

Spring profiles help segregating these. Specifically, we could put environment specific properties in files like application-dev.properties, application-prod.properties etc., and then define a property like spring.profiles.active=dev, to tell Spring which environment is’s running on. (Or, we could simply leave out defining spring.profiles.active, in which case the default profile will be active.)

3) Hide confidential properties

Some of the properties, like the database password of the production database, should not be visible to all the developers. So, I won’t put those in the application-prod.properties file inside our project. Instead, I’d have those in an application-prod.properties in the directory where the JAR will be deployed, or in a config sub-directory therein. These external files take precedence over those in the project.

3 thoughts on “Spring Boot – How Do You Externalize Application Properties

Leave a Reply

Your email address will not be published. Required fields are marked *