azurerm_storage_object_replication
- Use storage account id as properties.sourceAccount
and properties.destinationAccount
#20132
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.
Detailed context of this change can be found at: #19457 (comment). Quoted below:
Per: https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-overview#specify-full-resource-ids-for-the-source-and-destination-accounts
The ARM API-endpoint docs have also been updated: https://learn.microsoft.com/en-us/rest/api/storagerp/object-replication-policies/get?tabs=HTTP#objectreplicationpolicy
Fix #19457
Note that since the terraform schema is always using the storage account id before and after this PR, which means there would be no impact to existing users. As we are not reading the
properties.sourceAccount
andproperties.destinationAccount
to construct our TF state, but only used for import check (hence the change).Test