Google Secret Manager, Field Option
stvnksslr opened this issue · 1 comments
Feature Request
Is your feature request related to a problem? Please describe.
Kubernetes External Secrets Operator and many other tooling ecosystems encourage the use of json as the secret payload within the google secret manager. Teller is unable to unwrap or map these to env variables.
Describe the solution you'd like
Similar to other providers such as the AWS Secret manager provider I would like the option to pass a field attribute which would treat the payload as a map and allow me to map the K:V
lets say the contents of is {"MG_KEY":"shazam", "SMTP_PASS":"mailman"}
providers:
google_secretmanager:
env:
SMTP_PASS:
path: projects/<some project>/secrets/<some secret>/versions/1
currently it would return
SMTP_PASS={"MG_KEY":"shazam", "SMTP_PASS":"mailman"}
providers:
google_secretmanager:
env:
SMTP_PASS:
path: projects/<some project>/secrets/<some secret>/versions/1
field: SMTP_PASS
this should result in teller env returning
SMTP_PASS=mailman
thanks! should be resolved as part of Teller 2.0