Few improvements in a config file

[vadymus96]

Hello,

thanks for your effords for this product!

I work with massive .json files for .Net apps and faced with the problem of multiple entries in 'resource' chapter.
Previously I had an experience to use consul-template and we managed 3K keys in our templates. For now we expect to support ~1.4K keys with AKVA.

I'd suggest to:

• use multiple names for an each secret entry - to reduce the # of lines in the config file
• use '*' for as names in case that there is only one vaultBaseURL (names can be easy taken from a template file)
• use variables for vaultBaseURL - would help in case you have only one URL for all secrets

Thanks.

[chrisjohnson]

We recently merged 1.5.0 which adds support for all-secrets -- a feature to fetch every secret from a vault and store it in the Secrets list (as well as a toValues helper to make converting every secret into a large JSON blob) -- wonder if this helps your use case?

We'll also be looking to solve the vaultBaseURL repetition problem soon

[chrisjohnson]

Could you clarify more what you mean by

use multiple names for an each secret entry - to reduce the # of lines in the config file

[Serneum]

Could you clarify more what you mean by

use multiple names for an each secret entry - to reduce the # of lines in the config file

I think it would be something like

name: secret1 secret2 secret3
kind: secret
vaultBaseUrl: myvault.azure.net

That would reduce a lot of duplication when many secrets share the same vault

[vadymus96]

Serneum, absolutely. That's what I meant. Thanks.