SpotPlacementScore restructuring to RecommenderRP subdirectory - init…#36075
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
…cementScore APIs, remove unref'd example files
|
This is the first in a three part PR series that aims to do the same as the following PR: #36039 I am breaking the PR linked above into three parts to make the PR more understandable and easy to review. I will work on and merge each PR in sequence. PR order after discussion with Gary: |
| - code: DefinitionsPropertiesNamesCamelCase | ||
| reason: The property name contains abbreviations and need to keep it as upper case. | ||
| from: RecommenderRP.json | ||
| - code: BodyTopLevelProperties |
There was a problem hiding this comment.
Can you add a where clause to indicate which property you are suppressing? Add more entries if there're multiple instances.
There was a problem hiding this comment.
Removed BodyTopLevelProperties suppression
| - code: OperationsAPIImplementation | ||
| reason: The operations API is defined in a separate file. | ||
| from: RecommenderRP.json | ||
| - code: PathForResourceAction |
There was a problem hiding this comment.
Can you add a where clause to indicate which property you are suppressing? Add more entries if there're multiple instances.
| - code: PathForResourceAction | ||
| reason: This is not a valid scenario for the diskInspection and spotPlacementRecommender API as API Path does not match ARM Lint check formatting, requesting to suppress due to approval from reviewer. | ||
| from: RecommenderRP.json | ||
| - code: PathForNestedResource |
There was a problem hiding this comment.
Can you add a where clause to indicate which property you are suppressing? Add more entries if there're multiple instances.
…P' of https://github.com/Elina-L/azure-rest-api-specs into wenxliu/Part1SplitSpotPlacementScoreAPIIntoRecommenderRP
|
Add suppression for avocado as MULTIPLE_API_VERSION issue has already been aware by compute team. |
|
/azp run SDK Validation - Go |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…ial commit
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!
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.