go-kms-wrapping update for Azure Key Vault's Managed HSM offering [backport 1.7.x] #12957
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.
Backport of #12934 and #12952 to 1.7.x
The recently released update of
[email protected]
includes support for Azure KeyVault's Managed HSM offering. While the non-HSM-backed KeyVault offering was initially supported, support for the Managed HSM offering was broken because required customization wasn't exposed from the underlying library (namely,environment.KeyVaultDNSSuffix
).Respecting Azure SDK's
AZURE_AD_RESOURCE
variable (and mirroring it as aresource
field in the KeyVault seal config struct) allows us to use this type of KeyVault.Update to
go.mod
/go.sum
was created viago get -u github.com/hashicorp/[email protected]
followed by ago mod tidy
and ago mod vendor
(for 1.7.x).Note, per discussion between myself, Jeff Mitchell, Scott Miller, and Rachel Culpepper, we've decided updating from v0.5.16 to v0.6.8 (in g-k-w) to be fairly safe.
I've tested this locally with the KeyVault HSM and it functions as expected with the updated g-k-w.