Wenxliu/split diagnostic rp to individual package new #36673
Conversation
This file contains hidden or 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
Rename SpotPlacementScores.json to GenerateSpotPlacementScores.json Remove openapi-subtype: rpaas from readme.md Adding suppression for RecommenderRP Update suppressions file name from diagnostic.json to RecommenderRP.json Add required APIVersion to GetSpotPlacementScores.json [Monitor] Rename Ingestion TypeSpec directory (Azure#35991) Signed-off-by: Paul Van Eck <paulvaneck@microsoft.com> [DevTestLabs] Convert existing OpenAPI spec to TypeSpec spec (Azure#35346) Stable Version 2025-07-15 for Microsoft.Quota (Azure#35765) * Copy files from stable/2025-03-01 Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec. * Update version to stable/2025-07-15 Updated the API version from stable/2025-03-01 to stable/2025-07-15. * Added tag for 2025-07-15 in readme file * creates a new stable version for the enforcement endpoints * Adds the enforcement examples * adds GroupQuotaUsages folder * Adds enforcement definitions * Modifies the api version in the enforcement examples * adds proper api version for usages example * changes the retry after type and fixes typos * changes another description * renames GroupQuotasEnforcementResponse to GroupQuotaEnforcementStatus * formats object * Changes GroupQuotaEnforcementResponse to GroupQuotaEnforcementStatus. reverts unneccessary change in 2023-06-01 preview * ran prettier on 2023-06-01-preview for prettier check violation * changes object definition in preview version as well * resolves retry after issue * reverts the preview file objects Adding api-version input into GetSpotPlacementScores.json Run prettier Use forward slash [spec-model] Add cache in ctor, to re-use objects for the same path (Azure#36008) [Monitor Query Logs] Add Java customizations (Azure#36007) * [Monitor Query Logs] Add Java customizations * format [EngSys] Remove unnecessary workflow_dispatch triggers (Azure#36019) [dashboard] Remove properties order fix and fix location to be optional (Azure#36017) * remove properties order fix and fix location to be optional * remove needless suppression fix the back compatible for csharp (Azure#35965)
…ps://github.com/Elina-L/azure-rest-api-specs into wenxliu/SplitDiagnosticRPToIndividualPackageNew
…ps://github.com/Elina-L/azure-rest-api-specs into wenxliu/SplitDiagnosticRPToIndividualPackageNew
…son title and description
…ps://github.com/Elina-L/azure-rest-api-specs into wenxliu/SplitDiagnosticRPToIndividualPackageNew
…menderRP/main.tsp Co-authored-by: catalinaperalta <9859037+catalinaperalta@users.noreply.github.com>
microsoft-github-policy-service
bot
added
MySQL
Notification Hub
Monitor - Operational Insights
Operations Management
Peering
Policy Insights
PostgreSQL
RecoveryServices
Recovery Services Backup
Recovery Services Site-Recovery
Redis Cache
Relay
Scheduler
Search
Service Map
Service Bus
Service Fabric
Import Export
StorageSync
Storsimple
Stream Analytics
Subscription
Load Test Service
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!
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.