[enhancement] azurerm_storage_account
- Allow queue_encryption_key_type
and table_encryption_key_type
in more scenarios
#27112
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.
Community Note
Description
The alters the TF client-side validation to allow for
queue_encryption_key_type
andtable_encryption_key_type
to be utilized in more scenarios.The previous implementation restricted these properties to being set only when
account_kind
is setStorageV2
, however there are many other valid configurations. They are supported for allaccount_kind
values other than whenaccount_kind
is set toStorage
PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_storage_account
- Allow queue_encryption_key_type and table_encryption_key_type in more scenariosThis is a (please select all that apply):
Note
If this PR changes meaningfully during the course of review please update the title and description as required.