-
Notifications
You must be signed in to change notification settings - Fork 325
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
WPB-6577 Fix user creation conflict in SCIM #3914
WPB-6577 Fix user creation conflict in SCIM #3914
Conversation
1aafc87
to
48619a8
Compare
c4a5470
to
d6fe6fd
Compare
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.
looks good! i have one actual change request, otherwise looks good! let me know if you want to discuss this.
@@ -45,15 +46,17 @@ propsForInterpreter interpreter extract lower = do | |||
prop "insert/lookup" $ prop_insertLookup (Just $ show . void . extract) lower | |||
prop "insert/insert" $ prop_insertInsert (Just $ show . void . extract) lower | |||
|
|||
-- FUTUREWORK: Add prop tests for missing operations |
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.
have you given this a try? if not i can do that.
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.
You can go ahead, but maybe better in a separate PR.
-- something went wrong while storing the user in brig | ||
-- we can try clean up now, but if brig is down, we can't do much | ||
-- maybe retrying the user creation in brig is also an option? | ||
-- after clean up we rethrow the error so the handler returns the correct failure |
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.
what about not rethrowing, but looking up the status again once or twice? that'd make for swifter cleanup, especially when the batch job only runs once a day.
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.
It only rethrows if deleteScimUser
fails. AFAICT the deletion is synchronous.
Co-authored-by: Matthias Fischmann <[email protected]>
Co-authored-by: Matthias Fischmann <[email protected]>
For a description of the manual test approach, see comments of https://wearezeta.atlassian.net/browse/WPB-6577
Checklist
changelog.d