Skip to content
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

arm review: definition and assignment command categories should be sxs #1041

Merged
merged 3 commits into from
Oct 7, 2016

Conversation

yugangw-msft
Copy link
Contributor

@yugangw-msft yugangw-msft commented Oct 6, 2016

fix partial #1033. I moved definition related commands to under role definition or resource policy definition. Also fix some argument naming and completer related issues
fix #1020

@yugangw-msft yugangw-msft force-pushed the armreview1 branch 2 times, most recently from 83f734a to f88bed4 Compare October 6, 2016 21:46
Copy link
Member

@derekbekoe derekbekoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added one comment but LGTM apart from that

raise CLIError(err.format(resource_group_name))
scope = resource_id
scope = scope
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scope = scope?
This isn't needed right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

cli_command('resource policy list', PolicyDefinitionsOperations.list, factory)
cli_command('resource policy show', PolicyDefinitionsOperations.get, factory)
cli_command('resource policy update', update_policy_definition)
cli_command('resource policy definition create', create_policy_definition)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this going to create a group that only has one subgroup and no commands? If so, we should use the hyphenated version resource policy-definition ... instead. If resource policy has commands of its own then this is fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR just moved all policy definition commands from az resource policy to az resource policy definitions. So there are no commands under az resource policy now, rather just 2 groups, defintion and assignment. ARM team prefers this layout, and i agree.

cli_command('role delete', delete_role_definition)
cli_command('role create', create_role_definition)
cli_generic_update_command('role update',
cli_command('role definition list', list_role_definitions)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment here. If there are no commands under role, only the definition subgroup, then we should use a hyphenated version role-definition instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same with resource policy, role has 2 sub-groups definition and assignment

@yugangw-msft yugangw-msft merged commit 0f7e7f2 into Azure:master Oct 7, 2016
@yugangw-msft yugangw-msft deleted the armreview1 branch October 25, 2016 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants