How Can I Manage Database Credentials Dynamically in Spring Boot Across Multiple Environments?

Using Environment Variables in Spring Boot's application.properties

When developing a Spring Boot application that utilizes MySQL across multiple environments (local, CI/CD, production), it's essential to handle database credentials dynamically.

The Issue:

In application.properties, the typical approach is to hard code MySQL information. However, this introduces challenges when running the project in different environments, as each environment may have its own database configurations.

Proposed Solution:

To address the issue, the suggestion is to create system environment variables with appropriate values for each environment. These environment variables can then be used in application.properties to make the data source field dynamic.

Steps to Use Environment Variables:

1. Create System Environment Variables:
   Create the following system environment variables for MySQL configurations:

   • OPENSHIFT_MYSQL_DB_HOST
   • OPENSHIFT_MYSQL_DB_PORT
   • OPENSHIFT_MYSQL_DB_USERNAME
   • OPENSHIFT_MYSQL_DB_PASSWORD
2. Access Environment Variables:
   To access environment variables within Java code, use the System.getenv() method.

3. Incorporate Environment Variables in application.properties:
   Within application.properties, replace the hard-coded values with environment variables:

   spring.datasource.url = ${OPENSHIFT_MYSQL_DB_HOST}:${OPENSHIFT_MYSQL_DB_PORT}/"nameofDB"
   spring.datasource.username = ${OPENSHIFT_MYSQL_DB_USERNAME}
   spring.datasource.password = ${OPENSHIFT_MYSQL_DB_PASSWORD}

Alternative Approach:

Another recommended approach is to use Spring's profile-specific properties. By declaring the environment variable spring.profiles.active, Spring can automatically read the corresponding property file based on the active profile. For example:

• application-local.properties for local development
• application-ci.properties for CI/CD environment
• application-production.properties for production

In this approach, the application.properties file remains unchanged, while environment-specific configurations are defined in the profile-specific property files.

The above is the detailed content of How Can I Manage Database Credentials Dynamically in Spring Boot Across Multiple Environments?. For more information, please follow other related articles on the PHP Chinese website!