You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
Sops is unfortunately a little simplistic in how it looks for the .sops.yaml file. It expects the file to exist in the current working directory and then compares paths relative to that. I would like to collect my .sops.yaml files into a single configuration at the top of my tree to make it easier to share keys with patterns. I haven't found any way to do this that also works with helm-secrets.
Ideally helm-secrets would walk up the parent directories from the secrets.yaml file to find the .sops.yaml and then write the appropriate sops command relative to that directory.
The text was updated successfully, but these errors were encountered:
Sops is unfortunately a little simplistic in how it looks for the .sops.yaml file. It expects the file to exist in the current working directory and then compares paths relative to that. I would like to collect my .sops.yaml files into a single configuration at the top of my tree to make it easier to share keys with patterns. I haven't found any way to do this that also works with helm-secrets.
Ideally helm-secrets would walk up the parent directories from the secrets.yaml file to find the .sops.yaml and then write the appropriate sops command relative to that directory.
The text was updated successfully, but these errors were encountered: