Allow deletion of legacy suspended organizations - #2475
Draft
niemyjski wants to merge 7 commits into
Draft
Conversation
This file contains hidden or 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
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 changed
Clear suspension metadata before saving a soft-deleted organization.
Why
Organizations persisted by older billing flows can contain a short system marker in
SuspendedByUserId. The current model correctly requires object-ID-shaped user IDs, but deleting one of these legacy suspended organizations re-saved the record and returned HTTP 422 instead of completing the deletion.Verification
dotnet build Exceptionless.slnx --no-restore -m:1OrganizationEndpointTests: 104/104 passedNo production identifiers or customer data are included.