[Key Vault] Add 7.6-preview.2 to TSP

[mccoyp]

Data Plane API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

This integrates the changes from #31670 into TSP. The relevant API changes are in:

• Security.KeyVault.Certificates/models.tsp
• Security.KeyVault.Keys/models.tsp
• Security.KeyVault.Keys/routes.tsp

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

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
Swagger-Suppression-Process
to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next 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.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in 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.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ The required check named SDK azure-sdk-for-go has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 3 in the PR workflow diagram

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/security/keyvault/azcertificates	There is no API change compared with the previous version
Go	sdk/security/keyvault/azkeys	There is no API change compared with the previous version
Go	sdk/security/keyvault/azsecrets	There is no API change compared with the previous version
Python	azure-keyvault-administration	https://apiview.dev/Assemblies/Review/7643acce229a47c8a2d146efc30638fb?revisionId=6ba8e2c7f00a49cdad42dd27f725cfe1
Python	azure-keyvault-certificates	https://apiview.dev/Assemblies/Review/b2fdced96a5343cc972aac842b5f43fc?revisionId=c6a7b2955fee4834bfd13ad7b3bdac0e
Python	azure-keyvault-keys	https://apiview.dev/Assemblies/Review/9507cb5f29024272a1f19016634b6a25?revisionId=f7e624c0061544fc9adfdb70f2457884
Python	azure-keyvault-secrets	https://apiview.dev/Assemblies/Review/8103c86200684133980931472e4f8e24?revisionId=058743e80a4a44d8a5d78e2e87a55c06
TypeSpec	Security.KeyVault.BackupRestore	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5
TypeSpec	Security.KeyVault.Certificates	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5
TypeSpec	Security.KeyVault.Keys	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5
TypeSpec	Security.KeyVault.RBAC	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5
TypeSpec	Security.KeyVault.Secrets	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5
TypeSpec	Security.KeyVault.Settings	https://apiview.dev/Assemblies/Review/0529655b61bc404ebd37d2d5192ba45a?revisionId=04c9d6afcfbb41aea280a329025603f5

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.KeyVault
KeyVault

[heaths]

IIRC, these are the changes I remember reviewing. As long as the breaking change checks pass, this looks good to go.

Curious why all the Admin examples are newly added files, though. They don't seem wrong - just unexpected.

[heaths]

@mccoyp CredScan failed. Definitely take a look at that. Probably a fluke, though.

[mccoyp]

@mccoyp CredScan failed. Definitely take a look at that. Probably a fluke, though.

@heaths Yep, unfortunately the scanner thinks that "value": "A256CBCPAD" is exposing a secret in keys.json. Wes said that a refinement for the check should be coming in soonish

[mccoyp]

I learned from the TypeSpec team that specs should only include one preview version (and only include it if it's newer than the latest stable version), hence fbcc781. Swaggers should be left as-is and emitting from TSP won't cause issues since Swaggers for versions not in the spec won't be emitted.

[mccoyp]

The Go SDK automation failures (package 'azadmin' doesn't contain any exports) are from known bugs/limitations. Like in #30239, we can bypass these to merge when we hear from Managed HSM about whether a last enum change should be added. cc @karenychen