-
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
Instance pool usages #5894
Instance pool usages #5894
Conversation
…d instances get by instance pool
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
I plan to add instancePoolUsages.json and instancePools.json (not in this review) in a separate PR, so merging with just these files after validation and review is ok. |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
@johnpaulkee - The API signature and the response schema does not comply with ARM /usages contract. Please take a look - https://armwiki.azurewebsites.net/api_contracts/UsagesAPIContract.html |
We(ARM) will need to update the usages contract to cater to such scenarios. I Will have a proposal early next week. That way we can have consistency across Azure w.r.t getting usage data. |
...cation/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/instancePoolUsages.json
Outdated
Show resolved
Hide resolved
...cation/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/instancePoolUsages.json
Outdated
Show resolved
Hide resolved
...cation/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/instancePoolUsages.json
Outdated
Show resolved
Hide resolved
PR still needs to be updated per new usages spec (ARM). Gaurav is following up offline with the team. In reply to: 493736164 [](ancestors = 493736164) |
Acked on updated usages contract |
SDK Automation [Logs] (Generated from 73f5d68)Python: Azure/azure-sdk-for-python
Java: Azure/azure-sdk-for-java
Go: Azure/azure-sdk-for-go
JavaScript: Azure/azure-sdk-for-js
Ruby: Azure/azure-sdk-for-ruby
|
I've updated swagger based on updated usages contract.
@ravbhatnagar please validate when possible :) thank you. |
@ravbhatnagar @sanjaiganesh any update on ARM review? |
...cation/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/instancePoolUsages.json
Outdated
Show resolved
Hide resolved
Ping @ravbhatnagar for review. |
{ | ||
"swagger": "2.0", | ||
"info": { | ||
"version": "2.0", |
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.
this should be the api-version
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.
fixed. thanks @ravbhatnagar 👍
@johnpaulkee - looks good. just the api-version needs to be fixed. Signing off considering the api-version value will be fixed. |
Thanks @ravbhatnagar , I've updated api-version. |
ping @sergey-shandar for review. |
specification/sql/resource-manager/Microsoft.Sql/preview/2018-06-01-preview/usages.json
Show resolved
Hide resolved
…into instancePoolUsages
Thanks @sergey-shandar ! |
…5894) * AzureSphere: Fix of response of generateDefaultDeviceGroups action. Work item: https://dev.azure.com/msazuresphere/4x4/_workitems/edit/127676 * Azure Sphere fix typo on example
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.