Conversation

As I chatted on Gitter about, I have a different way that I'd like to use Vault, specifically being able to take a single path and reuse it between different environments instead of having to replicate the value into template-specific namespaces.

Here is my Pull Request for such a "mode" to do this. I added test cases, documentation, and kept it backwards compatible with the existing plugin implementation. I was trying to go for a very unbiased approach. Here's a sample config:

Note I also made it possible to use dynamic values in a Vault template path, since I would like to be able to use environment variables to dictate what Vault paths to access. For example, I run different localized versions of my application, so I want to set a SITE_COUNTRY environment variable to access a secret/country/<%= env_site_country %> list of values.

I'm not fully aware of the design philosophy of Tiller so I'm sure you'll have some feedback. The way I've designed the plugin here is exactly how I would like Tiller to work for me, but this may not be the same for everyone else.

1 check passed

1 check passed

Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.