external-secrets/kubernetes-external-secrets

Add ability to have plaintext, non-sensitive data rendered in the Secret's .spec.template.

jwtracy opened this issue · 4 comments

I would like to use the same lodash templating to render secret and non-secret data into a file.

The fact is that a file with both sensitive and non-sensitive environment specific data is still a sensitive file. It makes sense to create such a file in an ExternalSecret. For non-sensitive and repeated data like a callback URI, project ID, or even just environment name, these keys and values should be specified in the ExternalSecret.

Is there anyone who can help address this? I have proposed a PR, #790.

Also, this proposed revision is working for my company in production use cases.

Please see #864 for some info in current project standings :)

Thanks! I'll look into upgrading and porting!