-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[Hub Generated] Review request for Microsoft.CostManagement to add version preview/2019-04-01-preview #5956
[Hub Generated] Review request for Microsoft.CostManagement to add version preview/2019-04-01-preview #5956
Conversation
This reverts commit 177ac54.
…2019-03-01-preview to version 2019-04-01-preview
…nt-2019-04-01-preview
Can one of the admins verify this patch? |
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
Automation for azure-sdk-for-rubyThe 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-goNothing to generate for azure-sdk-for-go |
REST Spec PR 'Azure/azure-rest-api-specs#5956' REST Spec PR Author 'bgsky' REST Spec PR Last commit
Automation for azure-sdk-for-netA PR has been created for you: |
@praries880 @ravbhatnagar @NelsonDaniel @gahorowi This PR introduces 3 APIs: view, checkNameAvailability, and budget, by merging two earlier ones, #5895 and #5881. Please let us know if any comments to help schedule an API review meeting. |
Automation for azure-sdk-for-javaEncountered a Subprocess error: (azure-sdk-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmpe3zpd26h/rest/specification/cost-management/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmplqv0d9_2'] 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) |
REST Spec PR 'Azure/azure-rest-api-specs#5956' REST Spec PR Author 'bgsky' REST Spec PR Last commit
…nt-2019-04-01-preview
REST Spec PR 'Azure/azure-rest-api-specs#5956' REST Spec PR Author 'bgsky' REST Spec PR Last commit
@ravbhatnagar @praries880 @RyanBensonMSFT Following API review with Ryan, we updated Swagger files with following changes:
Please let us know if any comments, as we would like it signed off to onboard manifest. |
REST Spec PR 'Azure/azure-rest-api-specs#5956' REST Spec PR Author 'bgsky' REST Spec PR Last commit
@bgsky Two asks to help review this PR
|
@sanjaiganesh All the contents are new in this PR. No contents in old API version are included as there exist a few validation failures and we don't want conflicts as part of this PR. To help understand PR, it introduces two new APIs, budget and view, following CRUD operations |
...ent/resource-manager/Microsoft.CostManagement/preview/2019-04-01-preview/costmanagement.json
Show resolved
Hide resolved
...ent/resource-manager/Microsoft.CostManagement/preview/2019-04-01-preview/costmanagement.json
Show resolved
Hide resolved
...ent/resource-manager/Microsoft.CostManagement/preview/2019-04-01-preview/costmanagement.json
Show resolved
Hide resolved
"description": "User input name of the view. Required.", | ||
"type": "string" | ||
}, | ||
"scope": { |
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.
How is scope different than the Id of the resource? Your examples also just set this to empty string so I can't really follow what this is for.
No change on scope. It is part of resource id, and empty if the view is private/at tenant level. We would like scope in resource properties to pass to another resource, so it appears in response and user does not specify it in request body(included in request url). Please refer to an example of viewByResourceGroup as a use case.
SDK Automation [Logs] (Generated from 292ab85)Go: Azure/azure-sdk-for-go
Python: Azure/azure-sdk-for-python
Ruby: Azure/azure-sdk-for-ruby
|
@RyanBensonMSFT We updated spec and examples with the following parts:
|
...ent/resource-manager/Microsoft.CostManagement/preview/2019-04-01-preview/costmanagement.json
Show resolved
Hide resolved
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.
ARM review feedback appears to be resolved. Thanks
* Adding image validation status to fidalgo machine definition. * Add header in examples because validation says so
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: