Azure Stack Fabric.Admin Api update for GPU support#11092
Azure Stack Fabric.Admin Api update for GPU support#11092allenjzhang merged 6 commits intoAzure:masterfrom LingyunSu:ApiUpdateForGPU
Conversation
[Staging] Swagger Validation Report
️✔️ |
|
No pipelines are associated with this pull request. |
|
Thank you for copying the existing version into new folder for first commit. Changes looks good to me marking it ARMSignedOff. |
...zsadmin/resource-manager/fabric/Microsoft.Fabric.Admin/preview/2020-10-01/ScaleUnitNode.json
Show resolved
Hide resolved
|
second commit for easy review 9ceaa94 |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-js - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
allenjzhang
left a comment
There was a problem hiding this comment.
Please fix checks failures. The swaggers look fine. Once checks are green, it can be merged. Thx
|
No pipelines are associated with this pull request. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@allenjzhang Resource provider naming must follow the pascal case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/scaleUnits/{scaleUnit}/setGpuPartitionSize' |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@akning-ms , could you help to see if this is caused by our validation logic can't handles provider name with two dots? R3020 - PathResourceProviderNamePascalCase |
Yes. This case already supported in new Lint version which will enable soon. @jianyexi for awareness |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
* FabricAdmin Old version * Update on Fabric.Admin new version for GPU support * Fix CI validation issue * Validation fix * Add default response for setGpuPartitionSize * Add GPUP as a custom word
Azure Stack Fabric.Admin Api update for GPU support
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.