-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adding 2024-08-01 For Microsoft ToolchainOrchestrator From Private Spec Repo #30930
Adding 2024-08-01 For Microsoft ToolchainOrchestrator From Private Spec Repo #30930
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
Merge 08-01 version from private spec repo Referring PR: |
Please fill out the intake form at the top. The PR you linked that merged to the private is significantly different from this PR. Did you link the wrong PR from the |
I have filled the intake. Thanks for reminding. Here is the detail. I only pick up the content under "specification/symphony/resource-manager/Microsoft.ToolchainOrchestrator/preview/2024-08-01-preview/" from the private repo. We only have two versions "2024-04-01-preview" and "2024-08-01-preview". "2024-04-01-preview" is for private preview and "2024-08-01-preview" is for public preview. It looks like we shouldn't checkin the private preview version to the public, right? And the Typespec code also contains both of "2024-04-01-preview" and "2024-08-01-preview". So I may need some advises from ARM team, do we need to check in all the files under "specification/symphony/" ? Or we need to hide the private preview version? |
…FireDefend/azure-rest-api-specs into users/xigsun/updatesymphony1009
added typespec part, waiting for reviews from arm team |
I think it might be ok to just have 2024-04-01-preview in this repo |
Please fix the Swagger LintDiff errors in this PR. Looks like the use case is approved already in the private repo. Please add suppressions as needed in readme. |
…FireDefend/azure-rest-api-specs into users/xigsun/updatesymphony1009
I have checked in with both "2024-04-01-preview" and "2024-08-01-preview" now. For Swagger LintDiff errors, according to PRs in private repo, can you please add "Approved-LintDiff" tag to bypass? |
The jsons match to what is existing. We should be good there. |
suppressions added |
@@ -37,6 +37,10 @@ These settings apply only when `--tag=package-2024-08-01-preview` is specified o | |||
```yaml $(tag) == 'package-2024-08-01-preview' | |||
input-file: | |||
- Microsoft.ToolchainOrchestrator/preview/2024-08-01-preview/toolchainOrchestrator.json | |||
suppressions: | |||
- code: AvoidAdditionalProperties |
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.
Please add specific paths instead of ignoring for whole file.
@@ -46,4 +50,8 @@ These settings apply only when `--tag=package-2024-04-01-preview` is specified o | |||
```yaml $(tag) == 'package-2024-04-01-preview' | |||
input-file: | |||
- Microsoft.ToolchainOrchestrator/preview/2024-04-01-preview/toolchainOrchestrator.json | |||
suppressions: | |||
- code: AvoidAdditionalProperties |
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.
Please add specific paths instead of ignoring for whole file.
@@ -54,4 +57,7 @@ suppressions: | |||
- code: AvoidAdditionalProperties | |||
from: toolchainOrchestrator.json | |||
reason: Service design forces behavior | |||
- code: EnumInsteadOfBoolean |
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.
Please add specific paths instead of ignoring for whole file.
@@ -41,6 +41,9 @@ suppressions: | |||
- code: AvoidAdditionalProperties | |||
from: toolchainOrchestrator.json | |||
reason: Service design forces behavior | |||
- code: EnumInsteadOfBoolean |
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.
Please add specific paths instead of ignoring for whole file.
Please fix Swagger Avocado errors too |
Hi, @FireDefend. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
Hi, @FireDefend. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section 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 ApiView
comment 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 PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. 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.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.