Skip to content

Conversation

@vishrutshah
Copy link
Contributor

@vishrutshah vishrutshah commented Sep 8, 2017

Model ResourceUpdate is not a valid Azure resource. It should not be marked as x-ms-azure-resource: true.

cc:
@veronicagg @sarangan12

@vishrutshah vishrutshah self-assigned this Sep 8, 2017
@vishrutshah vishrutshah added ARM bug This issue requires a change to an existing behavior in the product in order to be resolved. Compute labels Sep 8, 2017
@veronicagg
Copy link
Contributor

LGTM, @amarzavery @lmazuel @shahabhijeet @jianghaolu @jhendrixMSFT could removing the extension from the spec cause breaking changes/problems on your SDKs?

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/compute/resource-manager/readme.md
Before the PR: Warning(s): 116 Error(s): 33
After the PR: Warning(s): 116 Error(s): 31

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@amarzavery
Copy link
Contributor

LGTM. FYI @huangpf @hyonholee

@lmazuel
Copy link
Member

lmazuel commented Sep 11, 2017

This should be fine

@vishrutshah
Copy link
Contributor Author

Thanks for the review everyone!!

@vishrutshah vishrutshah merged commit 6f5b90c into Azure:current Sep 11, 2017
@vishrutshah vishrutshah deleted the fix-wrong-resource-marking branch September 11, 2017 20:41
@AutorestCI
Copy link

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link

@AutorestCI
Copy link

vishrutshah added a commit to vishrutshah/azure-sdk-for-ruby that referenced this pull request Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARM bug This issue requires a change to an existing behavior in the product in order to be resolved. Compute

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants