Add "MakeBackupsImmutable" and "BackupStorageAccessTier" properties to LTRPolicies swagger file#26854
Merged
visingla-ms merged 4 commits intoAzure:mainfrom Dec 8, 2023
Conversation
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 |
|---|---|---|
| LongTermRetentionBackups.json | 2023-05-01-preview(9acb9f0) | 2023-05-01-preview(main) |
| LongTermRetentionPolicies.json | 2023-05-01-preview(9acb9f0) | 2023-05-01-preview(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.6) | new version | base version |
|---|---|---|
| package-preview-2023-05 | package-preview-2023-05(9acb9f0) | package-preview-2023-05(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L19 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L88 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L88 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L164 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L164 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionDatabaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L164 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L247 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L247 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionDatabaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L247 |
ResourceNameRestriction |
The resource name parameter 'backupName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L247 |
DeleteResponseCodes |
Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L310 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L362 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L374 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L374 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionDatabaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L374 |
ResourceNameRestriction |
The resource name parameter 'backupName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L374 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L434 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L446 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L446 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionDatabaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L446 |
ResourceNameRestriction |
The resource name parameter 'backupName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L446 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L511 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L523 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L523 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionDatabaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L523 |
ResourceNameRestriction |
The resource name parameter 'backupName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L523 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L588 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L600 |
ResourceNameRestriction |
The resource name parameter 'locationName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L672 |
ResourceNameRestriction |
The resource name parameter 'longTermRetentionServerName' should be defined with a 'pattern' restriction. Location: Microsoft.Sql/preview/2023-05-01-preview/LongTermRetentionBackups.json#L672 |
️⚠️Avocado: 1 Warnings warning [Detail]
| Rule | Message |
|---|---|
| The default tag contains multiple API versions swaggers. readme: specification/sql/resource-manager/readme.md tag: specification/sql/resource-manager/readme.md#tag-package-composite-v5 |
️️✔️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.
️️✔️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
|
|
Please address or respond to feedback from the ARM API reviewer. |
This was referenced Nov 28, 2023
Contributor
Author
|
/pr RequestMerge |
visingla-ms
approved these changes
Dec 8, 2023
arifibrahim4
pushed a commit
that referenced
this pull request
Feb 26, 2024
…o LTRPolicies swagger file (#26854) * added 2 new properties * fix typo and check failures * added missing properties to LTRPolicy
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
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.
Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)
ARMReviewlabel.Click here to see the diagram footnotes
Diagram footnotes
[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 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
Swagger-Suppression-Process
to get approval.
Getting help
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.