-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[RBAC] az ad group show: fix --group value treated as regex problem #12426
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
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ba43dc7
[RBAC] az ad group show: fix --group value treated as regex problem
arrownj e3ec50b
{RBAC} update syntax error of error message
arrownj 04f4e5a
{RBAC} retrieve domain from az ad signed-in-user show instead of hard…
arrownj a7588bf
{RBAC} refactor validate_group function
arrownj 11d1fbb
{RBAC} update recording file for test_graph_group_idempotent
arrownj 91e4051
{RBAC} update test_graph
arrownj 73d9004
{RBAC} update test_graph to use the right user info
arrownj 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 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
Oops, something went wrong.
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.
Personally, I think the usage of
has_next_filterlowers the cohesion of this function. It makes_validate_grouprely on the external logic and dependent between executions. I prefer not to exact the logic to_validate_groupbut put it in the originalvalidate_groupinstead.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'm also hesitated at it. @qianwens , want to hear your opinions.
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 it is correct to have _validate_group function or the handle exception logic in validate_group looks complicated. But for _validate_group, I agree that we should not raise different kind of error message based on the has_next_filter paramete. Currently _validate_group 's return logic is not predictable, sometime it return false, sometime it raise error, could you please refine the logic here, or you can replace this functio with _get_group_count to just return the count and let the validate_group to raise the exception
In reply to: 387564846 [](ancestors = 387564846)
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.
updated