Release machinelearningservices microsoft.machine learning services 2025 01 01 preview #32279
+61,095
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2024-10-01-preview to preview/2025-01-01-preview.
…e#32002) * Add ActualCapacityInfo contract changes to 2025 preview * Making updates to ActualCapacityInfo for Group Status
* Add quota apis * add location in swagger * add list available quota * add AvailableQuotaArmPaginatedResult * add location param * location param in examples * replace with location parameters * Removes azure-resource-manager-schemas from SDK automation. It can be re-added without reverting this commit. (Azure#30893) (Azure#31918) This change produces an extra warning but no obvious new errors. --------- Co-authored-by: Daniel Jurek <[email protected]>
* merge change from 2024-10-01-preview * add bugfix changes and new list api * Removes azure-resource-manager-schemas from SDK automation. It can be re-added without reverting this commit. (Azure#30893) (Azure#31918) This change produces an extra warning but no obvious new errors. --------- Co-authored-by: Daniel Jurek <[email protected]>
Co-authored-by: ZhidaLiu <[email protected]>
…Azure#32030) * Update mfe.json to add new content safety level property * prettier * more prettier * Update createOrUpdate.json with contentsafetylevel * Update get.json * Update list.json * Update update.json
* Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json
* add parent job name add parent job name * prettier prettier * prettier prettier
* add aad auth mode and cherrypick * prettier * remove getStatus change * reset mfe, add back aad auth * revert getStatus * prettier cmd * update mfe * prettier * cherrypick commit 1fc2fa1 * add newline back * add newline back
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
github-actions
bot
added
the
brownfield
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
AzureRestAPISpecReview
added
ARMReview
BreakingChangeReviewRequired
This was referenced Jan 22, 2025
* Lint diff fixes for Jan 25 preview * Update tag * Keep tag format consistent with other versions * resolve merge conflicts --------- Co-authored-by: ZhidaLiu <[email protected]>
ZhidaLiu
added
the
BreakingChange-Approved-Previously
ZhidaLiu
added
the
PublishToCustomers
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
AzureRestAPISpecReview
added
WaitForARMFeedback
ZhidaLiu
removed
the
WaitForARMFeedback
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
AzureRestAPISpecReview
added
the
WaitForARMFeedback
* Distillation ARM changes * Fix CSPell check * Fixed Prettier Failures * Fixed Model Validation * Updated PromptSetting description * Added Only Distillation Changes * Added definitions * removed unwanted changes * Ran Prettier * Updated swagger based on Vienna review * Updated Examples * Updated Description for Prompt Setting * Reorganized as per review comments * Updated examples * Ran Prettier * Handled review comments * Added Suppression.yaml file * Updated syntax * Fixed syntax * Added Suppressions in readme --------- Co-Authored-By: Qiaoqiao Zhang <[email protected]>
|
Please fix the Swagger LintDiff errors first. Also, the original PR doesn't seem to be reviewed/approved by ARM. It only has the breaking change approval. |
gary-x-li
added
the
ARMChangesRequested
openapi-pipeline-app
bot
removed
the
WaitForARMFeedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
the original PR with all the approval is: Release machinelearningservices microsoft.machine learning services 2025 01 01 preview #31600
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.