-
Notifications
You must be signed in to change notification settings - Fork 18
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
Error on startup: log.SetLogger(...) was never called; logs will not be displayed. #197
Comments
Downgraded to 1.8.0 image, and 1.7.0 image. Also seems to be an issue there. I guess it could be a configuration issue, but I haven't set anything specific that could affect it. Logging should 'just work' by default. |
FTR, I'm running a vanilla
|
The crossplane folks did it like we do in their provider template https://github.com/crossplane/upjet-provider-template/blob/9d7c6ff3c1a4419296f327952f9cbe852ff44f03/cmd/provider/main.go#L66
you can enable debugging like that:
The error you see was our fault tho, as we have a logging statement that causes that error message. However, I agree with you. |
I'll do what the crossplane folks did: https://github.com/crossplane/crossplane/pull/4403/files patch is in |
Image: xpkg.upbound.io/crossplane-contrib/provider-keycloak:v1.9.0
Crashes on startup...
The text was updated successfully, but these errors were encountered: