-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
OPA v0.27.0 crashes with s3_signing configured #3255
Labels
Comments
s3_signing
configured
Let's get this fixed ASAP and cut a point release. |
anderseknert
added a commit
to anderseknert/opa
that referenced
this issue
Mar 12, 2021
This was caused by new logger not getting properly initialized in NewClient call. Fixes open-policy-agent#3255 Signed-off-by: Anders Eknert <[email protected]>
srenatus
pushed a commit
that referenced
this issue
Mar 12, 2021
This was caused by new logger not getting properly initialized in NewClient call. Fixes #3255 Signed-off-by: Anders Eknert <[email protected]>
This was referenced Mar 12, 2021
Closed
Closed
Closed
chore(deps): Bump github.com/open-policy-agent/opa from 0.27.0 to 0.27.1
BrunoReboul/ram#147
Merged
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OPA v0.27.0 crashes with
s3_signing
configured as the service credential. This is due to the new logger implementation not being instantiated in theNewClient
call on theawsSigningAuthPlugin
.Steps to Reproduce the Problem
config.yaml
opa run --server --config-file config.yaml
The text was updated successfully, but these errors were encountered: