-
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
2020-09-01-preview Inference Endpoints and Deployments #10420
2020-09-01-preview Inference Endpoints and Deployments #10420
Conversation
Swagger pipeline can not start as the pull request has merge conflicts. |
Azure Pipelines successfully started running 1 pipeline(s). |
… resource deployments
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation
|
azure-sdk-for-go
|
azure-sdk-for-java
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
|
azure-sdk-for-net
|
azure-sdk-for-python
|
Can one of the admins verify this patch? |
azure-sdk-for-python-track2
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
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 Pipelines successfully started running 1 pipeline(s). |
…vices.json, added allowed sku types in deployment request
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Pull request contains merge conflicts. |
Pull request contains merge conflicts. |
…into 2020-09-01-preview-inference-specs
Azure Pipelines successfully started running 1 pipeline(s). |
"error": null, | ||
"authMode": "AMLTokenAuth", | ||
"uri": "", | ||
"deploymentWeights": {} |
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.
can add an example of the content of this map?
"tags": {}, | ||
"properties": { | ||
"description": "This is a test endpoint", | ||
"properties": {}, |
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.
do need this? can we remove in first iteration?
"modelURL" | ||
], | ||
"environmentConfigId": "EnvConfigURL", | ||
"codeAssetIds": [ |
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 is going to be just one right?
…and deployment resources as request body
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
…nflict with common types Sku definition
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Pull request contains merge conflicts. |
Due to changes in naming and structure, I will open a new PR with new names and changes. I will need another review for that. |
Pull request contains merge conflicts. |
Reopen to reuse the PR for name change |
Closing. Need to make a new PR. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.