fix service account user always triggers user events #1246
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AssahBismarkabah
requested review from
francis-pouatcha,
jonasvoelcker and
Thendo20
Thendo20
reviewed
Jan 8, 2025
Workaround for CI fails because ubuntu-latest version is 24.04 which doesn't support python 3.7. Signed-off-by: Thomas Darimont <[email protected]>
AssahBismarkabah
force-pushed
the
878-service-account-user-always-triggers-update-user-in-keycloak-during-import
branch
from
8a09d01 to
fd86b07
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: fix service Account User which always triggers update of user events.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #878Special notes for your reviewer:
other events may still occur due to other properties, as the realm export from Keycloak contains properties that users may not have defined in the realm configuration.
PR Readiness Checklist:
Complete these before marking the PR as
ready to review:CHANGELOG.mdrelease notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR