-
Notifications
You must be signed in to change notification settings - Fork 332
Add Identifier annotation to DefaultActiveRolesProvider #1111
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
Add Identifier annotation to DefaultActiveRolesProvider #1111
Conversation
dimas-b
left a comment
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.
This change is innocuous in the current codebase. The added identifier could be used to look up an ActiveRolesProvider by custom producers in environments where multiple implementations are available.
|
My mistake, as CI shows the change is not innoccuous 😅 This can be resolved by adding a custom producer method similar to this: polaris/quarkus/admin/src/main/java/org/apache/polaris/admintool/config/QuarkusProducers.java Line 43 in 3816cfd
|
|
|
||
| @Produces | ||
| public ActiveRolesProvider activeRolesProvider( | ||
| @ConfigProperty(name = "quarkus.active-roles-provider.type") String persistenceType, |
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.
We probably need to set this config in application.properties to default
This is usually an indicator that the server did not start for some reason... The root cause may be hidden in logs (especially if they are redirected). |
dimas-b
left a comment
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 👍
…apache#24) * add identifier * add producer * add to config Co-authored-by: Eric Maynard <[email protected]>
When debugging with Quarkus, @RichardLiu2001 and I noticed that
DefaultActiveRolesProviderdoesn't have anIdentifiercurrently. This means that if we add a new implementation ofActiveRolesProvider, the runtime can fail with: