-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add owner-name label on resources #3608
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
14bb258
Add owned-by annotation on resources
super-harsh e26f3ec
Change annotation to owner-name label
super-harsh 8d43cea
Add header
super-harsh 307bde8
minor fix for map assignment
super-harsh 9befda8
Minor method refactor
super-harsh 22d5803
Add owner group.kind/ArmId label
super-harsh 371ad08
fix SetOwnerGroupKindLabel check
super-harsh d33d1a6
Add group kind label to only kubernetesReferences
super-harsh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
owner-name
orowner
would be clearer thanowned-by
.Do we also need to think about
owner-group-kind
or something as well, for extension resources such as roleassignment?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep makes sense - Users can filter through annotations but isn't as easy as with labels.
Made the changes to add label instead of annotation and changes the name to
owned-by
toowner-name
.Not very sure about if adding
owner-group-kind
would bring much value.. since user can anyway filter based on owner-name - which is more specific rather than filtering all resources based on just group + kind?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not having
owner-group-kind
forces the user to do another query to discover the owner type if they don't already know it. I think there's value in making it easy/obvious.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! and that applies to only resources which are KubernetesReferences?