azurerm_iot_dps
- fix update of old resource without data_residency_enabled
#20632
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.
Fix #20587
azurerm_iot_dps
created with early provider version doesn't have propertydata_residency_enabled
set, which cannot be set (even to its default value) any more. Fixing the issue by splitting the Create/Update, and use the existing iotdps in the update call (data_residency_enabled
isForceNew
so no need to operate it in Update)