Repository navigation
fix: keep relationships consistent when retiring objects - #514
Merged
Merged
Conversation
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## next #514 +/- ##
==========================================
+ Coverage 81.99% 82.11% +0.12%
==========================================
Files 252 256 +4
Lines 41202 41521 +319
Branches 5311 5512 +201
==========================================
+ Hits 33782 34096 +314
+ Misses 7326 7323 -3
- Partials 94 102 +8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
🎉 This PR is included in version 4.24.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Why
Retiring or replacing an object could leave its relationships out of sync. Revocation only moved separate relationship objects—not references stored inside other objects. The API also allowed ordinary relationships to inactive objects.
What changes
subtechnique-ofandrevoked-bylinks are preserved.revoked-byremains an exception.Checks
1,208 API tests passed. Real API and browser checks covered the paired workflow. Local tests used a temporary loopback workaround for a machine-specific port collision.
Operational note
Graph writes are serialized to prevent races. A crashed writer can leave a lock that needs operator cleanup; the recovery steps are documented.
Companion frontend change: mitre-attack/attack-workbench-frontend#972
Follow-up (out of scope)
Repair stale embedded backlinks left behind by earlier buggy updates. This PR fixes future updates but does not clean up existing stale metadata. The team still needs to decide how to perform that cleanup—for example, a one-time migration—and whether a recurring Data Quality check is warranted. No historical-backlink repair is included in this PR.