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

fix for issue 998 - uniquely get a generic resource using name, group, type and provider info #1003

Merged
merged 1 commit into from
Aug 2, 2016

Conversation

martinsawicki
Copy link

fix for #998

Ability to uniquely get a generic resource in case of duplicate names in same resource group

GenericResources#getByGroup() has been removed since it is not going to have a predictable behavior on GenericResources. Normally getByGroup() impls can already assume the resource type, but for generic resources, that cannot be assumed.
Instead, a new overload for GenericResources#get() has been added, requiring the 4 params uniquely identifying a resource

…se of duplicate names in same resource group

GenericResources#getByGroup() has been removed since it doesn't make sense on GenericResources
Instead, a new overload for GenericResources#get() has been added, requiring the 4 params uniquely identifying a resource
@martinsawicki martinsawicki changed the title fix for issue 998 - unquely get a generic resource using name, group, type and provider info fix for issue 998 - uniquely get a generic resource using name, group, type and provider info Aug 2, 2016
@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@anuchandy anuchandy merged commit 0fdd748 into Azure:master Aug 2, 2016
jianghaolu pushed a commit to jianghaolu/azure-sdk-for-java that referenced this pull request Feb 27, 2017
fix for issue 998 - uniquely get a generic resource using name, group, type and provider info
jianghaolu pushed a commit to jianghaolu/azure-sdk-for-java that referenced this pull request Feb 27, 2017
fix for issue 998 - uniquely get a generic resource using name, group, type and provider info
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