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 Component Omnibus #1033

Closed
12 of 15 tasks
JasonRShaver opened this issue Oct 5, 2016 · 1 comment
Closed
12 of 15 tasks

ARM Component Omnibus #1033

JasonRShaver opened this issue Oct 5, 2016 · 1 comment
Assignees
Labels
ARM az resource/group/lock/tag/deployment/policy/managementapp/account management-group Resource Manager

Comments

@JasonRShaver
Copy link
Contributor

JasonRShaver commented Oct 5, 2016

The following feedback came out of our ARM review meeting

  • Update ARM to use general api-version logic and follow-up [@yugangw-msft, if no supplied, we will query provider for the latest api-version]
  • Resource delete should not have --parent (@yugangw-msft, we will keep it to maintain consistent interface across show, delete and tag )
  • Resource exists should be removed (as it is not supported by ARM)
  • Support auto-complete for --resource-type
  • Remove resource tag command (@yugangw-msft, we will keep, as it is working pretty well with resource id)
  • Resource management commands should work accept resource ID
  • Policy
    • Definitions and assignments should both be groups
  • Policy Assignment
    • commands should use --scope, not --resource-id (@yugangw-msft fixed by PR#1041)
    • List should remove --show-all (@yugangw-msft reviewed with @vivsriaus, due to api inconsistency, we will by default do strict scope match, but offer option to let people do loose match to show everything on group or individual resource, same deal when you use -g or --scope)
  • Provider
    • List should show resource type and location (requires 2nd call for location info) (@yugangw-msft, verified azure-cli does and with more comprehensive content)
    • Register should return right away and not wait
  • Group
    • Update does not have a use for --add (@yugangw-msft, chatted with colleagues , and we decide to keep as it can be used for adding tag)
  • Deployment
    • Create should allow default name using same naming logic (if not created server side)
    • Create should support @ syntax template from an uri (edited by @yugangw-msft)
    • Remove 'exists'
@mayurid
Copy link
Member

mayurid commented Oct 12, 2016

moving to Sprint 5 as this is spanning 2 sprints.

@mozehgir mozehgir added the ARM az resource/group/lock/tag/deployment/policy/managementapp/account management-group label Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARM az resource/group/lock/tag/deployment/policy/managementapp/account management-group Resource Manager
Projects
None yet
Development

No branches or pull requests

5 participants