Describe the bug
Storage accounts, which were deployed with the 0.10.0 version of the Storage Account module, cannot be re-deployed with the release 0.11.0 of the Storage Account module.
The deployment fails with the error Status Message: The property 'isNfsV3Enabled' was specified in the input, but it cannot be updated as it is read-only.
This is because of change implemented in #3290 in response to #3106. While I think this change is necessary, it causes issues for older storage accounts. The "older" storage accounts, deployed with CARML 0.10.0 have isNfsV3Enabled=false set, the new module version 0.11.0 is only able to set isNfsV3Enabled=true or isNfsV3Enabled=null, but it cannot set isNfsV3Enabled=false.
To reproduce
- Deploy a storage account using CARML release 0.10.0
- "Upgrade" CARML to 0.11.0
- Address breaking changes/renamed parameters (i.e.
skuName)
- Re-deploy the storage account
Code snippet
No response
Relevant log output
No response
Describe the bug
Storage accounts, which were deployed with the 0.10.0 version of the Storage Account module, cannot be re-deployed with the release 0.11.0 of the Storage Account module.
The deployment fails with the error
Status Message: The property 'isNfsV3Enabled' was specified in the input, but it cannot be updated as it is read-only.This is because of change implemented in #3290 in response to #3106. While I think this change is necessary, it causes issues for older storage accounts. The "older" storage accounts, deployed with CARML 0.10.0 have
isNfsV3Enabled=falseset, the new module version 0.11.0 is only able to setisNfsV3Enabled=trueorisNfsV3Enabled=null, but it cannot setisNfsV3Enabled=false.To reproduce
skuName)Code snippet
No response
Relevant log output
No response