fix(tenancy): require scoped cloud-key agreement - #29
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Description
This change tightens device tenancy resolution by requiring cloud-key agreement when resolving scoped devices.
Previously, scoped lookups only matched on device identifiers and tenancy boundaries. In environments where the same device key can exist across different cloud contexts, this could allow ambiguous matches or resolve the wrong device. By including
analytics.cloudpublickeyin every scoped filter path, device resolution now verifies both tenancy scope and cloud ownership.The update improves isolation between cloud environments, reduces the risk of cross-cloud device collisions, and makes device resolution more deterministic and secure. Tests were updated to ensure the cloud key is consistently applied across project-scoped lookups.