Connect to Multiple Vault Secrets Engines

spring-cloud / spring-cloud-config

External configuration (server and client) for Spring Cloud

Apache License 2.0

1.97k stars 1.29k forks source link

Connect to Multiple Vault Secrets Engines #1270

Open kevin-thompson opened 5 years ago

kevin-thompson commented 5 years ago

Since Vault allows for multiple secrets engines, it seems reasonable to expect that one might use multiple engines for the same project. For example, Vault supports database secrets engines that manage, well, database secrets, but many other properties will just be key-values. It would be nice to pass a list of secrets engines into the "backend" property rather than it just accepting a single secrets engine.

kamalakarp commented 5 years ago

@kevin-thompson - This week I added the vault namespace changes and it'll be good to add other secret engines as well. I can contribute the related code changes and review the changes needed.

atdiff commented 4 years ago

What's the status on this? Would be a useful feature

spencergibb commented 4 years ago

Were waiting for votes before this gets prioritized.

luroto commented 2 years ago

Hi there! Just out of curiosity, is there any updates related to this issue? Or is there any workaround? I've been searching for some time and I didn't get a clue related to this, besides to use different paths inside the very unique secret engine. Thanks in advance!