You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi there, apologizes if this is standard operating functionality but I was curious on why I could not inject the spring.config.import property on command line -D argument but instead required to have a profiled file name for Spring Cloud Vault to work.
For example...........I have a "dev" and "qa" configuration. For both of the run commands for either configuration, I would like to simply inject at the command line:
-Dspring.config.import=vault://
Using command line seems to have no effect. I have to have an application yml/properties with the name of the profile in src/main/resources to work. Such as:
application-dev.yml
application-qa.yml
And the contents inside of the files, nothing more than:
spring:
config.import:
- 'vault://'
Is there a way to do what I'm looking to do to globally and agnostic to the environment set the spring.config.import property without having to have a profiled app config file?
The text was updated successfully, but these errors were encountered:
hi there, apologizes if this is standard operating functionality but I was curious on why I could not inject the spring.config.import property on command line -D argument but instead required to have a profiled file name for Spring Cloud Vault to work.
For example...........I have a "dev" and "qa" configuration. For both of the run commands for either configuration, I would like to simply inject at the command line:
-Dspring.config.import=vault://
Using command line seems to have no effect. I have to have an application yml/properties with the name of the profile in src/main/resources to work. Such as:
And the contents inside of the files, nothing more than:
Is there a way to do what I'm looking to do to globally and agnostic to the environment set the spring.config.import property without having to have a profiled app config file?
The text was updated successfully, but these errors were encountered: