Yash/ekm hsm public preview#29775
Open
notyashhh wants to merge 9 commits into
Open
Conversation
- New cmdlets: New/Update/Get/Test/Remove-AzKeyVaultEkmConnection and Get-AzKeyVaultEkmConnectionCertificate (via KeyVaultEkmClient). - Add -ExternalKeyId to Add-AzKeyVaultKey to create EKM-backed external keys. - Bump Azure.Security.KeyVault.Administration 4.9.0-beta.1 / Keys 4.11.0-beta.1. - Local Azure.Core 1.57.0 override (required by the new betas); to be removed once the central Azure.Core bump lands.
- Rename the New/Update-AzKeyVaultEkmConnection parameter -Host to -HostName (alias Host) to avoid shadowing PSCmdlet.Host. - Add platyPS help markdown for the 6 EKM cmdlets. - Add EkmConnectionHelper unit tests (host/path-prefix/cert loading). - Add EkmConnection scenario tests + script (LiveOnly; record once the HSM is up).
- PSKeyVaultKey now exposes ExternalKeyId (from the Track2 key's external key). - Add -ExternalKeyId to Add-AzKeyVaultKey.md (syntax + parameter). - Assert ExternalKeyId in the external-key scenario test.
…y fixes - Rename the 6 EKM connection cmdlets to include ManagedHsm in the noun (New/Update/Get/Test/Remove-AzKeyVaultManagedHsmEkmConnection, Get-AzKeyVaultManagedHsmEkmConnectionCertificate) for Az.KeyVault consistency. - Add dedicated external-key parameter sets so -ExternalKeyId cannot be combined with -KeyType/-Size/-CurveName/-Exportable (matches CLI fail-fast); guard -KeyOps. - Add -ServerCn alias on -ServerSubjectCommonName (CLI parity with --server-cn). - Fix HsmResourceId resolution bug in Add-AzKeyVaultKey.
…anary - Rename 6 EKM help markdown files to *-AzKeyVaultManagedHsmEkmConnection. - Read + write ops verified against canary MHSM (Get/Test/Certificate/Update/ external key); connection restored to original state. Help bodies finalize via GenerateHelp.
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
…uires 5.5.0; central Azure.Core 1.57 stays for CI only
…Vault only Path B (central 1.56->1.57) broke the whole repo's Analyze + all test legs: Az.Accounts ships Azure.Core 1.56 in its lib from a separate pin the central bump doesn't update, so every module referenced 1.57 but loaded 1.56. Reverting to the isolated KeyVault-local 1.57 override (builds 0/0).
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
1 participant
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.
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.