-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Update Application Insights Schema to support WorkItemConfig operations #5870
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
Conversation
Automation for azure-sdk-for-rubyEncountered a Subprocess error: (azure-sdk-for-ruby)
Command: ['/usr/local/bin/autorest', '/tmp/tmpytq_4_vn/rest/specification/applicationinsights/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpahxixbbr'] 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/@[email protected]/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@[email protected]/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/@[email protected]/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-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
|
@TomMilos can you look this over as well to make sure it's good for CDS? |
REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit
Automation for azure-sdk-for-netA PR has been created for you: |
...ghts/resource-manager/Microsoft.Insights/stable/2015-05-01/componentWorkItemConfigs_API.json
Show resolved
Hide resolved
...ghts/resource-manager/Microsoft.Insights/stable/2015-05-01/componentWorkItemConfigs_API.json
Show resolved
Hide resolved
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
...ghts/resource-manager/Microsoft.Insights/stable/2015-05-01/componentWorkItemConfigs_API.json
Outdated
Show resolved
Hide resolved
...sights/resource-manager/Microsoft.Insights/stable/2015-05-01/examples/WorkItemConfigGet.json
Outdated
Show resolved
Hide resolved
Just a heads-up, but this resource type schema is a violation of the RPC. Given that this was already available like this, I'm not going to block these changes. However, ARM API review will block additions of new resource types that are not compliant with the RPC documented at https://github.com/Azure/azure-resource-manager-rpc #Pending Refers to: specification/applicationinsights/resource-manager/Microsoft.Insights/stable/2015-05-01/componentWorkItemConfigs_API.json:304 in dba4561. [](commit_id = dba4561, deletion_comment = False) |
majastrz
left a comment
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.
I added some comments. Please take a look.
...ghts/resource-manager/Microsoft.Insights/stable/2015-05-01/componentWorkItemConfigs_API.json
Show resolved
Hide resolved
REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit
majastrz
left a comment
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.
Looks like all my comments were addressed. Thanks!
dsgouda
left a comment
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.
LGTM
|
@debugthings Pleazse fix the model validation errors reported here |
|
@dsgouda All good now it seems. Thanks for all your help |
* .NET SDK Resource Provider:'ApplicationInsights' REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit * .NET SDK Resource Provider:'ApplicationInsights' REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit
…#6137) * .NET SDK Resource Provider:'ApplicationInsights' REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit * .NET SDK Resource Provider:'ApplicationInsights' REST Spec PR 'Azure/azure-rest-api-specs#5870' REST Spec PR Author 'debugthings' REST Spec PR Last commit
Updating the componentWorkItemConfigs_API.json swagger def to address S360 work item.
Changes
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.