Page MenuHomePhabricator

Update repository identities after all mutations to users and email addresses
ClosedPublic

Authored by epriestley on Nov 14 2019, 7:49 PM.
Tags
None
Referenced Files
F15488081: D20914.id49858.diff
Thu, Apr 10, 7:12 PM
F15486301: D20914.id49858.diff
Thu, Apr 10, 6:25 AM
F15474922: D20914.diff
Sun, Apr 6, 1:58 PM
F15455432: D20914.id49836.diff
Sun, Mar 30, 12:21 AM
F15438550: D20914.id.diff
Wed, Mar 26, 1:26 AM
F15431144: D20914.diff
Mar 24 2025, 10:47 AM
F15418876: D20914.diff
Mar 21 2025, 2:00 AM
Unknown Object (File)
Feb 21 2025, 12:54 PM
Subscribers
None

Details

Summary

Ref T13444. Currently, many mutations to users and email addresses (particularly: user creation; and user and address destruction) do not propagate properly to repository identities.

Add hooks to all mutation workflows so repository identities get rebuilt properly when users are created, email addresses are removed, users or email addresses are destroyed, or email addresses are reassigned.

Test Plan
  • Added random email address to account, removed it.
  • Added unassociated email address to account, saw identity update (and associate).
    • Removed it, saw identity update (and disassociate).
  • Registered an account with an unassociated email address, saw identity update (and associate).
    • Destroyed the account, saw identity update (and disassociate).
  • Added address X to account A, unverified.
    • Invited address X.
    • Clicked invite link as account B.
    • Confirmed desire to steal address.
    • Saw identity update and reassociate.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Nov 19 2019, 5:42 PM
This revision was automatically updated to reflect the committed changes.