Skip to content

Conversation

@eelcokos
Copy link
Contributor

When trying the example with the "-Force" parameter, the cmdlet doesn't remove the assignment from a resource group. When running the same cmdlet without "-Force" than the assignment is removed. Maybe "-Confirm" was actually intended in the example?

Description

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • the markdown help files have been regenerated using the commands listed here

When trying the example with the "-Force" parameter, the cmdlet doesn't remove the assignment from a resource group. When running the same cmdlet without "-Force" than the assignment is removed. Maybe "-Confirm" was actually intended in the example?
@adxsdkps
Copy link
Collaborator

Can one of the admins verify this patch?

@VeryEarly VeryEarly self-assigned this Jun 22, 2020
@VeryEarly
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly VeryEarly merged commit 1b4f7dd into Azure:master Jun 22, 2020
@eelcokos eelcokos deleted the patch-2 branch June 30, 2020 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants