Allow Vault backend to be pattern based

I cant seem to find a way to do this, nor does it look like its possible from looking at the code. However I would like it to be possible to make the vault backend have an option to be pattern based similar to the git backend.

This would allow for a number of different scenarios.

1. Currently if I enable multiple backend types in my config server(vault and git) and I do not pass the vault token I am unable to access any properties from the server, a missing token exception is thrown. If I was able to add a pattern to match based off of the profile I could then have apps access the config server without the token and be able to get their properties. Apps that need to access the vault backend as well could just add the vault profile and specify the token. This would allow for the use of the same server for apps that don't require vault access as well as apps that do.

2. this would allow for setting up multiple vault backends , just like the ability to have multiple git repos.

Is there a way to do this currently ? If not, is this something that is worth implementing?

Start by reading the existing git backend pattern handling and the vault backend configuration and selection paths. Check whether profile-based matching and multiple vault backends are supported, then define tests for the no-token and vault-profile scenarios; done means both backend types can coexist without an unnecessary token failure.