chore(keycloak): update permissions listener to 0.2.0#192
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ec58b3be6d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ARG KEYCLOAK_MINECRAFT_VERSION=1.1.2 | ||
| ARG KEYCLOAK_PERMISSIONS_EVENT_LISTENER_VERSION=0.1.0 | ||
| ARG KEYCLOAK_PERMISSIONS_EVENT_LISTENER_SHA256=31a34dbae8a337b2e6cff2629dd399a9b0f338287da6e3199a2338e877f2b446 | ||
| ARG KEYCLOAK_PERMISSIONS_EVENT_LISTENER_VERSION=0.2.0 |
There was a problem hiding this comment.
This version bump is a breaking configuration change for deployments that set KC_SPI_EVENTS_LISTENER_PERMISSIONS_EVENTS_REALM to a realm name. In v0.2.0 the provider parses the setting as a set of realm IDs and matchesRealm checks only event.realmId; v0.1.0 also accepted event.realmName. Since this image still documents the variable as accepting an ID or name, those deployments will start normally but silently skip all permission invalidation events after the upgrade. Please either document/enforce the migration to realm IDs (and comma-separated IDs) or keep name compatibility.
Useful? React with 👍 / 👎.
|
Replaced by a feat-classified PR with a matching branch and commit type. |
Pull Request
Description
Updates the Keycloak permissions event listener to v0.2.0, pins the verified release asset checksum, and aligns the documented build defaults.
Type of Change
Related Issues
Testing
linux/amd640.2.0Checklist