Problem/Motivation
Data may end up unsynchronized in Keycloak and Drupal.org; so having a way to identify what is not in sync will be useful.
Steps to reproduce
N.A.
Proposed resolution
Create a new drupalorg-keycloak-integrity-check drush command to do that.
Remaining tasks
Write the code.
Review.
User interface changes
New drush command.
API changes
N.A.
Data model changes
N.A.
Issue fork drupalorg-3448936
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
marvil07 commentedComment #4
marvil07 commentedComment #5
marvil07 commentedThis is ready for review.
The
3448936-kc-integrity-checkand related MR !260 contains the proposed code.The
3448936-kc-integrity-check-batchbranch is there just for comparison.Using Batch API helped a bit with the performance of the implementation, but the cost was a lot higher complexity.
I would say that performance gain may not be worth in this case.
Hence, no MR opened related to this branch.
Comment #8
drummMerged!
Comment #10
marvil07 commentedRe-opening, for a follow-up, no need for extra issue.
Comment #12
marvil07 commentedAdded new MR https://git.drupalcode.org/project/drupalorg/-/merge_requests/275 with an extra option to use a local file instead of KC REST API.
Comment #25
drummWe may add more special handling for edge cases, but this is all good to close.