Add the missing x-ms-skip-url-encoding for some swagger specs#26194
Add the missing x-ms-skip-url-encoding for some swagger specs#26194
x-ms-skip-url-encoding for some swagger specs#26194Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Swagger Generation Artifacts
|
Generated ApiView
|
e7d0759 to
70c0869
Compare
70c0869 to
7694e68
Compare
|
@rkmanda Would you please look at this PR as it has been hanging for 3 months and I'm about to leave it closed if no one from the swagger team gonna review it. |
|
@rkmanda Would you please look at this PR as it has been hanging for 3 months and I'm about to leave it closed if no one from the swagger team gonna review it. |
The PR was signed off by ARM in October. The PR review workflow diagram calls out what you should have done to request a merge which clearly hasnt been followed. Please do the needful to request merge. The turnaround time for merges is 24 hours. |
|
The go SDK check is also failing. So pl follow the documentation to get that to green or reach out to the owners to get an approval. |
|
Do u have permission from these different RP owners to make this change on their behalf? |
|
@rkmanda Thank you for your response. The background of my PR is that we have some internal tooling that will do something similar to the swagger live validation things, but not quite the same. During the processing, we identified these issues among different specs. You can find some latest versions of those specs have that missing tag added, which indicates they were leaked in the ARM review and this PR just fixes that up. IMO, there should be a linter to catch those issues at the first place. As mentioned above, the CI failures flagged are not introduced by this PR, but just triggered by the it. I'd prefer not complicate this PR to involve not intended fixes. WDYT? |
|
Hi, @magodo. 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, @magodo. 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
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.