Add missing string static enrichment property to Azure Event Grid 2023-12-15-preview Swagger#26613
Merged
zizw123 merged 24 commits intoAzure:mainfrom Nov 10, 2023
a-hamad:main
Merged
Add missing string static enrichment property to Azure Event Grid 2023-12-15-preview Swagger#26613zizw123 merged 24 commits intoAzure:mainfrom a-hamad:main
zizw123 merged 24 commits intoAzure:mainfrom
a-hamad:main
Conversation
…3-06-01-preview and use it as baseline for 2023-12-15-preview
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| EventGrid.json | 2023-12-15-preview(9abfeea) | 2023-12-15-preview(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️🔄LintDiff inProgress [Detail]
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
AzureRestAPISpecReview
added
the
ReadyForApiTest
This was referenced Nov 8, 2023
JeffreyRichter
added
the
Approved-BreakingChange
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
zizw123
reviewed
Nov 9, 2023
| "description": "*** Error Responses: ***\n\n * 400 Bad Request.\n\n * 500 Internal Server Error." | ||
| "description": "Error response returned if request was unsuccessful.", | ||
| "schema": { | ||
| "$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/ErrorResponse" |
zizw123
added
the
ARMSignedOff
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
Member
Author
|
pr /RequestMerge |
Member
Author
|
@zizw123 I am requesting merging as I don't see the Automated merging requirement met is enabled even with the breaking change being approved and ARM approved. |
zizw123
approved these changes
Nov 9, 2023
Alancere
added
the
Approved-SdkBreakingChange-Go
Member
Author
|
pr /RequestMerge |
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
This was referenced Nov 10, 2023
This was referenced Nov 10, 2023
zman-ms
pushed a commit
that referenced
this pull request
Jan 10, 2024
…3-12-15-preview Swagger (#26613) * First commit: Copy over latest event grid swagger for API version 2023-06-01-preview and use it as baseline for 2023-12-15-preview * Add new features for API Version 2023-12-15-preview * Address prettier issues + spelling check + add 2023-12-15-preview to readme files * Add missing example and some LintDiff * remove readonly property: * fix enum lintdiff issue * fix description * fix array x-ms-identifiers: [] * fix prettier check * fix more lindiff issues * fix lintdiff error * fix lindiff issues * fix example * Fix example * add suppressions for LintDiff as they are false positibe * add arm-id on array items for action group to fix sdk generation error * fix x-ms-arm-id for action group item * Add missing operation and its example file * fix prettier check * fix example * trigger tasks * Add missing string static enrichment property to 2023-12-15-preview * Add missing required
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequestedis removed from your PR. This should cause the label
WaitForARMFeedbackto be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see
Getting helpsection below.Purpose of this PR
What's the purpose of this PR? Check all that apply. 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 Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReviewlabel.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
Swagger-Suppression-Process
to get approval.
Getting help
and https://aka.ms/ci-fix.