-
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
Key rotation swagger change #11965
Key rotation swagger change #11965
Conversation
Swagger Validation Report
|
Rule | Message |
---|---|
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: Microsoft.KeyVault/preview/7.3-preview/keys.json#L82:5 |
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: Microsoft.KeyVault/preview/7.3-preview/keys.json#L1134:5 |
️⚠️
LintDiff: 0 Warnings warning [Detail]
- Linted configuring files (Based on source branch, openapi-validator v1.9.2 , classic-openapi-validator v1.1.6 )
- Linted configuring files (Based on target branch, openapi-validator v1.9.2 , classic-openapi-validator v1.1.6 )
Rule | Message |
---|---|
R2005 - LongRunningResponseStatusCode |
A 'PUT' operation 'FullRestoreOperation' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: Microsoft.KeyVault/preview/7.3-preview/backuprestore.json#L131 |
R2005 - LongRunningResponseStatusCode |
A 'PUT' operation 'SelectiveKeyRestoreOperation' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: Microsoft.KeyVault/preview/7.3-preview/backuprestore.json#L226 |
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L477 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L519 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L531 |
|
The operation 'CreateCertificate' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.KeyVault/preview/7.3-preview/certificates.json#L458 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
ModelValidation: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
OBJECT_ADDITIONAL_PROPERTIES |
Additional properties not allowed: expirationTime Url: Microsoft.KeyVault/preview/7.3-preview/keys.json#L2268 |
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
|:speech_balloon: AutorestCore/Exception|"readme":"keyvault/data-plane/readme.md",
"tag":"package-preview-7.3-preview",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"keyvault/data-plane/readme.md",
"tag":"package-preview-7.3-preview",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
The following errors/warnings exist before current PR submission:
|:speech_balloon: AutorestCore/Exception|"readme":"keyvault/data-plane/readme.md",
"tag":"package-preview-7.3-preview",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
NewApiVersionRequired reason: |
...eyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/examples/GetKeyPolicy-example.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
}, | ||
"description": "The action that will be executed." | ||
}, | ||
"KeyPolicyAttributes": { |
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.
Are any of these values required?
….3-preview/keys.json Co-authored-by: Heath Stewart <[email protected]>
Hi, @qinl-li. 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 @qinl-li, Your PR has some issues. Please fix the CI sequentially by following the order of
|
@@ -2149,23 +2159,31 @@ | |||
"properties": { | |||
"rotationEnabled": { | |||
"type": "boolean", | |||
"required": false, |
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.
Nit: the default for required
is false
so this isn't necessary, but doesn't hurt.
…into Microsoft.KeyVault-DP-7.3-preview-KeyAutoRotation
...a-plane/Microsoft.KeyVault/preview/7.3-preview/examples/UpdateKeyRotationPolicy-example.json
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Show resolved
Hide resolved
…into Microsoft.KeyVault-DP-7.3-preview-KeyAutoRotation
@qinl-li can you please resolve comments as you make changes so we can better spot changes? |
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
Hi, @qinl-li. 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, @qinl-li. 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. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Outdated
Show resolved
Hide resolved
specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json
Show resolved
Hide resolved
@lmazuel can you merge this? I haven't permissions when there are validation errors, which is expected for KV for now. |
* Key rotation swagger change * Run PrettierCheck * fixed spellcheck error * Update specification/keyvault/data-plane/Microsoft.KeyVault/preview/7.3-preview/keys.json Co-authored-by: Heath Stewart <[email protected]> * Update based on comments * fix prettier failure * Update Api names * Add custom words * Update to key rotation policy * Remove key rotation policy from response * Remove required * fix validation error * remove parameter force * Rotate api should be post * udpate description * Update UpdateKeyRotationPolicy-example * Update names * Microsoft.KeyVault-DP-7.3-preview-KeyAutoRotation * Update Co-authored-by: Jack Lichwa <[email protected]> Co-authored-by: Heath Stewart <[email protected]>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.