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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_storage_account_customer_managed_key
- support for cross-tenant customer-managed keys #20356azurerm_storage_account_customer_managed_key
- support for cross-tenant customer-managed keys #20356Changes from all commits
0c1fdaf
c66a8aa
0e5a109
eeae8e2
5bb43e2
484d530
2b37a46
0390f74
c127236
1c51368
ae3f97b
5f735be
0d6b847
d9a14d3
707a94b
490a9aa
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW we're intentionally not exposing
key_vault_uri
as a field across the Provider, since we're unable to determine within the Provider when the Key Vault is (temporarily) inaccessible or (permanently) gone - so unfortunately that's not something we can ship without introducing other issues (and even if we made an exception for this resource, we'd get asks for this on other resources, which would have the same issue).Instead, we should be able to look this up given the
tenant_id
, which would solve this in a different manner - WDYT?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the replay @tombuildsstuff, I've replied to a similar ask previously here:
#20356 (comment)
The bottom line is that this key vault is completely outside of the control of the entity that sets up the encryption. Common use case would be a customer providing a key which they want to use to encrypt their own data. This means we don't have access to lookup any metadata for that key.
This also mimics Azure's UI used for setting up storage account encryption, where you can either specify the keyvault using ID or URI. URI is the only possible option when setting up the cross tenant AD App.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation @Sewci0. Looking at the docs for this configuration, it seems like referencing the URI is the best/only way forward in this case, so I think it's ok to add this.