-
Notifications
You must be signed in to change notification settings - Fork 0
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
Spsh-1635 #109
base: main
Are you sure you want to change the base?
Spsh-1635 #109
Conversation
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.
Trivy found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
As much as I would like to embrace the technical benefits we could achieve through this PR (the ability to build Keycloak plugins and providers), I have a slight issue accepting 82 new vulnerabilities in something as crucial as our Keycloak repo. Suggestion: Keep Keycloak base image, do multi-stage build using the ubi8 image (COPY --from) and have the ubi8 container discarded before finishing. |
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.
see comment above
No description provided.