This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 155
doesnt decode secret file #124
Comments
Ok the solution was because of the way the file was named. I assumed that it would just look at the file contents and if there is a sops then it would decode it. However it seemed to only accept |
is it possible to change this pattern at all ? so it can be |
Yes this is a real annoyance. I created ticket #128 for this. Seems like the fix should be really easy to allow additionally secrets-something which is more intuitive for describing the secrets file. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a secret file, that is my dockerconfigjson for a private repository.
I am able to encode this json string no worries, and then decode it no worries manually.
However passing it into comand:
I look at the output and it is the same encoded value.
when this is compiled. the b64enc is equal to the encoded value.
ENC[AES256_GCM,data:....]
I have another secret file, which actually works no problem. So it must be something to do with the value. it is quite a long value because its a json string.
The text was updated successfully, but these errors were encountered: