-
Notifications
You must be signed in to change notification settings - Fork 860
-
Notifications
You must be signed in to change notification settings - Fork 860
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
Upgrade from v3.8.1 to v3.9.0 causes "could not load AWS config" error #1552
Comments
Hey, can you test something for me please? Are you able to build your own sops version? If so, could you look at the following comment and change Line 193 in 8b5cafe
to // keytype + toMap make a unique combination per key type
valueMap := v.ToMap()
delete(valueMap, "created_at")
delete(valueMap, "enc")
key := fmt.Sprintf("%T/%v", v, valueMap) and report if this fixes your problem? It could be that the "make keys unique" is causing your issue. |
Since the encrypted file contains two keys, and the 3.9.0 error message also mentions two keys, I don't think this is related to making keys unique since both keys seem to be tried. My guess is that this is related to some updated dependency. I don't use any KMS (and have access to none) so I have no way to test this myself... |
hi |
I've upgraded our sops binary from v3.8.1 to v3.9.0. Without changing any encrypted file, our pipeline jobs started failing due to this new error. I've put together a few steps to replicate the issue. Let me know if you need any more info!
The text was updated successfully, but these errors were encountered: