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
Yep, I have a feeling that the pathing isn't too smart. Ultimately sopstool should resolve every path added/used as relative to .sops.yml wherever it is (hopefully including ../). At a minimum it should resolve it as direct-ancestor of .sops.yml regardless of the cwd
I have a ruby project directory that looks like this:
from within the my_gem directory, I can decrypt using this command
sopstool decrypt secrets/my_secrets.sops.yaml
However, I can't decrypt that same file when using an absolute path
sopstool decrypt /src/my_gem/secrets/my_secrets.sops.yaml --configpath /src/my_gem
This seems to have something to do with the
.sops.yaml
configuration. This is the configuration where I was experiencing the problem:If I change the
encrypted_files
to the absolute path, it starts workingThe text was updated successfully, but these errors were encountered: