Add ability to fallback to properties file in the case of unit test environment

[TimGonz-AVIO]

I attempted to run a MUnit test with an app configured to use the Vault properties provider without having a connection to the Vault instance (and also without having the specific property available but the Vault instance running). I received an error like the following:

Couldn't find configuration property value for key ${vault::secret/url.path}

It listed trying to use environment properties provider and configuration-attribute provider composed of (Vault properties provider, <configuration-properties file="test.properties"> ...). I created a test properties file containing the following key/value pairs in an attempt to help it resolve the property with no luck:

secret/url.path=get
vault::secret/url.path=get
"vault::secret/url.path"=get

Could we include a fallback to property file resolution within the Vault properties provider in the case of situations like this? My thought is that if a Jenkins server was running in isolation from the environments where the Vault instances were running, or in the case you're running locally and don't have access to the Vault instances.

[Kevin44]

Is this something that is going to be worked on in the future or has it been put on hold indefinitely. My company would like this option and have been considering writing something ourselves. Thanks!

[adesjardin]

@Kevin44 - This feature is in progress actually and should be complete/merged later this week