-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Improve error feedback for Keycloak dev service startup #28533
Conversation
} else { | ||
LOG.debugf("Realm %s resource is not available", realmPath.get()); | ||
errors.add(String.format("Realm %s resource is not available", realmPath.get())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put the full error message here but it's actually not used, it's just a marker.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @gsmet, sure, we can accumulate errors this way and add more useful error message along the way, sorry you had to update so many functions to pass the errors list around :-)
So just to make it clear: I add the errors there just as flags. The usual logger is used as I don't want to break the flow of the logging (it's important to understand what's going on). So having the errors in the list is just a nice way to say |
That sounds OK |
Fixes #25809
I decided to go for something specific because this use case is actually rather specific. We need to somehow be able to propagate errors that are not fatal and actually display the full log in this case.