-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
EventGrid: Swagger for API Version 2019-06-01 #6003
Conversation
Automation for azure-sdk-for-rubyEncountered a Subprocess error: (azure-sdk-for-ruby)
Command: ['/usr/local/bin/autorest', '/tmp/tmplasi2vi2/rest/specification/eventgrid/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpdd_hp4ul'] AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4370/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4370/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@microsoft.azure_autorest-core@2.0.4370/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
autorest_core_1.Shutdown();
^
ReferenceError: autorest_core_1 is not defined
at process.on (/root/.autorest/@microsoft.azure_autorest-core@2.0.4370/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
at emitOne (events.js:121:20)
at process.emit (events.js:211:7)
at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
return binding.close(fd);
^
Error: EBADF: bad file descriptor, close
at Object.fs.closeSync (fs.js:612:18)
at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
at process._fatalException (bootstrap_node.js:391:26) |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
"tags": [ | ||
"Topics" | ||
], | ||
"summary": "List topics under a resource group.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iterms -> items
"summary": "List topics under a resource group.", | |
"description": "The number of results to return per page for the list operation. Valid range for top parameter is 1 to 100. If not specified, the default number of results to be returned is 20 items per page.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx. fixed
Can one of the admins verify this patch? |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-netA PR has been created for you: |
REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit
REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit
"description": "*** Error Responses: ***\n\n * 400 Bad Request.\n\n * 500 Internal Server Error." | ||
} | ||
}, | ||
"x-ms-examples": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the earlier version had some more examples here, can you please double-check if they are still required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx. Fixed
@sarangan12 Can you please approve/merge the change if no more concerns? |
Adding ARM Review since this is a new version |
@sarangan12 |
This is same as 2019-02-01-preview version. New resource type domains is being added. This has already been reviewed and approved by ARM for the preview. Signing off from ARM side. |
* .NET SDK Resource Provider:'EventGrid' REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit * .NET SDK Resource Provider:'EventGrid' REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit
* .NET SDK Resource Provider:'EventGrid' REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit * .NET SDK Resource Provider:'EventGrid' REST Spec PR 'Azure/azure-rest-api-specs#6003' REST Spec PR Author 'ahamad-MS' REST Spec PR Last commit
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.