docs: clarify resource identity and add community blog post#308
Merged
mathieu-benoit merged 2 commits intoJul 6, 2026
Merged
Conversation
Signed-off-by: Prashantkumar Khatri <khatri2105104@st.jmi.ac.in>
Signed-off-by: Prashantkumar Khatri <khatri2105104@st.jmi.ac.in>
a7c38af to
0c0e411
Compare
mathieu-benoit
approved these changes
Jul 6, 2026
mathieu-benoit
left a comment
Contributor
There was a problem hiding this comment.
LGTM, great clarification and addition, thanks @ShantKhatri!
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 is the motivation?
The current documentation does not explicitly detail how resource UIDs are constructed or how identity matching works under the hood. Clarifying this process helps developers understand how to correctly use the id field and realize that "shared resources" are simply the result of identity matching rather than a separate primitive in the spec. Additionally, we want to surface a recent community blog post that dives deep into this resolution process.
What does this change do?
What is your testing strategy?
Is this related to any issues?
No. Adding these has been discussed with @mathieu-benoit over Slack.
Have you read the Contributing Guidelines?