Document SHM Key Vault role requirement - #2651
Open
sylvesterkaczmarek wants to merge 1 commit into
Open
Conversation
sylvesterkaczmarek
marked this pull request as ready for review
August 15, 2026 18:41
llewelld
approved these changes
Aug 17, 2026
llewelld
left a comment
Contributor
There was a problem hiding this comment.
Thanks for this contribution.
I hit this issue during a test deploy recently and having this in the docs would have saved me a lot of time, so this is a useful addition in my view. Moreover the text is clear, and precise, so just what's needed. A nice addition.
Author
|
Thanks very much for the kind feedback and for reviewing this. Glad the addition is useful and hopefully saves others some time during deployment too. |
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
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.
Fixes #2638.
SHM deployment creates and accesses the Pulumi encryption key in Azure Key Vault. The deployment documentation currently lists Contributor permissions, but that role does not grant the required Key Vault data-plane actions.
Document the additional Key Vault Administrator requirement alongside the existing subscription Contributor requirement so deployment prerequisites match the permissions the CLI actually needs.