-
Notifications
You must be signed in to change notification settings - Fork 878
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
decrypt.Data
does not support ini
store by default
#548
Comments
Oversight!
Maybe, yeah. We should probably just |
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 15, 2019
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 16, 2019
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 16, 2019
added #549 to try and address this. |
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 16, 2019
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 16, 2019
dnozay
added a commit
to dnozay/sops
that referenced
this issue
Oct 16, 2019
autrilla
added a commit
that referenced
this issue
Oct 26, 2019
fix for #548 - handle .ini files in `decrypt.Data`, add other helper
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a reason why the cli supports
.ini
files out of the box, butdecrypt.Data(...)
doesn't?should it be using
DefaultStoreForPath
instead?The text was updated successfully, but these errors were encountered: