-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ref(backup): Refine dangling model resolution
Certain models that do not have unambiguous relationship to any RelocationScope root model (ex: Organization, User, etc) are termed "dangling", because filtering them down is done by simply moving up the model dependency tree from the root to the leaves - we have to double back and look at these "dangling" innner leaves instead. See https://tinyurl.com/27z4x6tk for more info; the `SnubaQuery`, `TimeSeriesSnapshot`, and `Email` models are all dangling in this manner. This PR changes the dangling resolution logic a bit: all `Excluded` relocation scope models are no longer considered dangling. Additionally, a few models that didn't quite get over the hump for "dangling" resolution during status analysis, but are obviously so, are marked as such. Issue: getsentry/team-ospo#203
- Loading branch information
1 parent
63df56c
commit 11fcf1d
Showing
2 changed files
with
59 additions
and
40 deletions.
There are no files selected for viewing
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
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