-
Notifications
You must be signed in to change notification settings - Fork 16
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
Optionally toggle secretFilenameRegexp
#3
Comments
Hi @igaskin, This behavior is inherited from Helm secrets plugin (the Helm plugin which inspired Helm Sops). Indeed, getting secret filename regexp from .sops.yaml file could be nice. However, I won't have the time to work on it soon. But we're open to pull requests ;-) |
teejaded
referenced
this issue
in teejaded/helm-sops
Nov 3, 2020
GUI
pushed a commit
to GUI/helm-sops
that referenced
this issue
Nov 8, 2022
Update docs to remove mention of secrets.yaml naming convention
hbollon
pushed a commit
that referenced
this issue
Jun 23, 2023
Fixed in #9 which is released 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use case
Restricting the decryption of files to those with the word "secrets" in the filename enforces a regex that can also be included as part of the
.sops.yaml
configuration file as apath_regex
. This can produce a strange user-experience, in which the.sops.yaml
is inclusive a given set of files, but the regex inhelm-sops
excludes it.https://github.com/mozilla/sops#210using-sopsyaml-conf-to-select-kmspgp-for-new-files
The text was updated successfully, but these errors were encountered: