-
Notifications
You must be signed in to change notification settings - Fork 568
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
gotmpl
secrets are not supported
#1878
Comments
Hi there in the upcoming version of helm-secrets (mention that helm plugin install will use master) the logic has been changed here. helm-secrets will always append suffix, not only on .yaml files. Additionally, the parameter In context of .yaml files, it will not break helmfile since replace .yaml by .yaml.dec is the same like just append dec. But the change in helm-secret will break with files other than .yaml. Additionally, to increase the compatibility, there is a new option for helm secret dec to just print the path of the decrypted file location. That should avoid some custom logic like that Lines 276 to 288 in c623730
|
hm, seems to decrypt fine and it seems like I'm running into another issue. |
unfortunately, decrypting the
.yaml.gotmpl
files doesn't work. they're not parsed as templates.there're two independent problems here:
helm-secrets doesn't like JSON (not YAML) sops container (and sops defaults to JSON if the extension is not
.yaml
, but.yaml.gotmpl
. I have a patch for this.helmfile
seems to assume that the decrypted file should be a template. not really sure what's going on, but I think it just assumes thesecrets
decrypted file is a YAML file, not a.yaml.gotmpl
.The text was updated successfully, but these errors were encountered: