[Key Vault] Create Security Domain library

[mccoyp]

Description

This is a new library that is mostly generated directly from TypeSpec. The goal of this library is to provide a track 2 Security Domain client for the CLI, as well as external customers. There are currently no plans for shipping this library in other languages.

Initial preview timeline: public preview release by April 8th, 2025 May 6th, 2025.

Customer library request: Azure/azure-cli#29998

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API Change Check

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

azure-keyvault-securitydomain

[github-actions]

Hi @mccoyp. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[xuzhang3]

@mccoyp any update of this SDK?

[mccoyp]

@xuzhang3 Our current estimate is that we'd like to release an initial Python preview in early April.

[pvaneck]

Doesn't look like black, pylint, mypy, etc. are actually being run in the pipeline. I believe you need to update ci.yml in sdk/keyvault to include the new artifacts/package.

[pvaneck]

Overall, LGTM. A couple inline comments.

Also, looks like many of the analyze pipeline steps are still not checking this package because of compatibility filters filtering this package out (Python 3.9+ is required by this package, but these jobs still run on 3.8). This should be resolved with: #40499. But I trust that you've verified black/mypy/pylint/pyright are passing locally.

[p3ck]

How close are we to this being in a release? Thanks

[mccoyp]

Hi @p3ck, a release should be out next week, with a current date target of May 6th.

[azure-sdk]

API change check

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

azure-keyvault-securitydomain

[pvaneck]

Looks like test failures are from the secrets package, and it's just some mocks that need adjusting.

You might also need to adjust the aka.ms link to point to something else until the docs are generated/pushed after release to make the Analyze step green in the release pipeline.

[mccoyp]

/check-enforcer override

[mccoyp]

/check-enforcer override