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

2018-05-01 APIs for Microsoft.Resources #2976

Merged
merged 7 commits into from
Jun 5, 2018
Merged

Conversation

Tiano2017
Copy link
Contributor

@Tiano2017 Tiano2017 commented Apr 30, 2018

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Apr 30, 2018

Automation for azure-sdk-for-node

Encountered a Subprocess error: (azure-sdk-for-node)

Command: ['/usr/local/bin/autorest', '/tmp/tmpr9dc_x3p/rest/specification/resources/resource-manager/readme.md', '--license-header=MICROSOFT_MIT_NO_VERSION', '--node-sdks-folder=/tmp/tmpr9dc_x3p/sdk', '--nodejs', '[email protected]/autorest.nodejs@^2.1.43']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4262; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4278)
   Loading AutoRest extension '@microsoft.azure/autorest.nodejs' (^2.1.43->2.1.59)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
[Exception] No input files provided.

Use --help to get help information.

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/resources/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/resources/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

"tags": [
"Deployments"
],
"operationId": "Deployments_Delete",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deployments_Delete [](start = 24, length = 18)

We should use a different operation Id, so that it doesn't conflict with the existing RG level deployment APIs below

"/subscriptions/{subscriptionId}/providers/Microsoft.Resources/deployments/{deploymentName}": {
"delete": {
"tags": [
"Deployments"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deployments [](start = 11, length = 11)

Deployments_SubscriptionLevel ? (or something better, to differentiate from the original APIs)

@AutorestCI
Copy link

AutorestCI commented Apr 30, 2018

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
AutorestCI/azure-libraries-for-java#154

@AutorestCI
Copy link

AutorestCI commented Apr 30, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2570

@AutorestCI
Copy link

AutorestCI commented Apr 30, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#1970

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/resources/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/resources/resource-manager/readme.md

⚠️0 new Warnings.(0 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

"$ref": "#/parameters/SubscriptionIdParameter"
}
],
"responses": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't have a good story for the default error responses today. This is common for all our APIs. I think we can address that separately.

@@ -2046,6 +2361,10 @@
},
"Deployment": {
"properties": {
"location": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We cant make this change in existing API-version. Existing SDKs will not be able to deserialize.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. I'm adding it to a new api-version.

"in": "body",
"required": true,
"schema": {
"$ref": "#/definitions/Deployment"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is legacy but why do we have input model different from output. LIke in input we take Deployment and in output we give back DeploymentExtended. Couldnt we have used the same one and if there are properties which are not settable, we could have marked them as readonly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was fixed.

@azuresdkci azuresdkci requested a review from anuchandy May 2, 2018 02:33
@anuchandy anuchandy added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 2, 2018
@AutorestCI
Copy link

AutorestCI commented May 31, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@Tiano2017 Tiano2017 changed the title <Do Not Merge> New APIs for Microsoft.Resources New APIs for Microsoft.Resources May 31, 2018
@Tiano2017
Copy link
Contributor Author

@anuchandy, @mcardosos this PR is ready for review. Please help take a look.

@Tiano2017 Tiano2017 changed the title New APIs for Microsoft.Resources 2018-05-01 APIs for Microsoft.Resources Jun 4, 2018

``` yaml $(tag) == 'package-resources-2018-05'
input-file:
- Microsoft.Resources/stable/2018-05-01/resources.json
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done. @shahabhijeet can you take one more look?

@sergey-shandar
Copy link
Contributor

@amarzavery do you have any idea why nod.js is failing?

@anuchandy
Copy link
Member

@shahabhijeet are you ok with the C# config changes now?

@anuchandy
Copy link
Member

@Tiano2017 just talked to @shahabhijeet, he has couple of questions around C# config section, please sync with him.

Copy link
Member

@shahabhijeet shahabhijeet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@Tiano2017
Copy link
Contributor Author

@anuchandy Synced up with Abhijeet, and he signed off.

@anuchandy anuchandy merged commit 91f504b into Azure:master Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.