Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Secret Manager, Field Option #184

Closed
stvnksslr opened this issue Sep 5, 2023 · 1 comment
Closed

Google Secret Manager, Field Option #184

stvnksslr opened this issue Sep 5, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@stvnksslr
Copy link
Contributor

stvnksslr commented Sep 5, 2023

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

@stvnksslr stvnksslr added the enhancement New feature or request label Sep 5, 2023
@jondot
Copy link
Contributor

jondot commented May 15, 2024

thanks! should be resolved as part of Teller 2.0

@jondot jondot closed this as completed May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants