Skip to content

Fix the bug of Get-AzResource with api-version #10712

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
merged 1 commit into from
Dec 18, 2019

Conversation

wyunchi-ms
Copy link
Contributor

@wyunchi-ms wyunchi-ms commented Dec 13, 2019

Description

To fix issue #9797. It's caused that server doesn't return the avaiable api-version list of some sub resource type.
We will use the api-version list of it's parent resource type if it's api-version list is empty.

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

@adxsdkps
Copy link
Collaborator

Can one of the admins verify this patch?

@wyunchi-ms wyunchi-ms changed the title Fix the bug that Get-AzResource will not return what we expect when t… Fix the bug of Get-AzResource with api-version Dec 13, 2019
…he server forget to return the api-version of the resource type
@msJinLei msJinLei merged commit b21faa0 into Azure:master Dec 18, 2019
@wyunchi-ms wyunchi-ms deleted the fix-resourceType-apiVersion branch June 5, 2020 13:16
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