-
Notifications
You must be signed in to change notification settings - Fork 151
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
Overriding configuration in profile specific files does not seem to work #697
Comments
Profile selection is subject to Spring Boot. Spring Cloud Vault uses Boot's ConfigData API and the failures in bootstrapping the Vault Client are a consequence of the provided configuration. You're mentioning If you would like us to spend some more time helping you to diagnose the problem, please provide a minimal yet complete sample that reproduces the problem. |
Hi there, I've noticed that I'm having the same issue, ie. i run my app with the flag |
I had the same issue. Setting the So try to add |
I'm trying to integrate my Spring Boot app with Vault for loading secrets. The app runs on PCF environment so the main configuration file (application.properties) is configured appropriately. For local development, the vault authentication is done via a regular token. So I have created application-local.properties file with appropriate configuration for local development. Then I set the "Active Profiles" value to "local" under the run/debug configuration.
Problem is that when I try to start the app in IDEA, I get the following error. So it's clear that the vault related properties mentioned in application-local.properties are not being picked up during startup.
Here is the complete pom and main application.properties and application-local.properties files.
I have generated the deployment artifact using command
mvn clean install
and then tried to run the app usingjava -jar demo-0.0.0.1-snapshot.jar -Dspring.profiles.active=local
.Since I'm passing the profile, I was expecting that configuration from the application-local.properties file will be picked up but from the stacktrace it seems like the main configuration file is being read.
pom.xml
application-local.properties
application-local.properties
The text was updated successfully, but these errors were encountered: