feat(infrahub): enhance peer node handling with unique identifier man…#111
feat(infrahub): enhance peer node handling with unique identifier man…#111
Conversation
|
Caution Review failedFailed to post review comments WalkthroughThe pull request modifies relationship handling in the Infrahub adapter to implement unique_id-based lookups for peer items. Instead of always constructing new peer model instances, the code now derives a unique_id from peer model identifiers, checks if the peer item exists in the client store, and reuses cached instances when available. If not found, it creates and stores the peer item. This pattern is applied consistently across one-to-one relationships, one-to-one paths, and one-to-many relationships, with relationship values assigned as the peer item's unique_id. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying infrahub-sync with
|
| Latest commit: |
0897996
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a534dcc6.infrahub-sync.pages.dev |
| Branch Preview URL: | https://atg-20260217-infrahub.infrahub-sync.pages.dev |
When syncing data in hierarchy it would not lookup from store before getting from infrahub.
Summary by CodeRabbit
Release Notes