Upgrade azurerm terraform provider from v3.112.0 to v3.117.0 #4220
Conversation
…gate storage account deployment issue microsoft#4004
Unit Test Results0 tests 0 ✅ 0s ⏱️ Results for commit 9727088. ♻️ This comment has been updated with latest results. |
|
/test 2932cff |
|
🤖 pr-bot 🤖 🏃 Running tests: https://github.com/microsoft/AzureTRE/actions/runs/12482142357 (with refid (in response to this comment from @jonnyry) |
|
/test-extended 2932cff |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/12483029966 (with refid (in response to this comment from @jonnyry) |
|
/test-destroy-env |
|
Destroying PR test environment (RG: rg-tref33f08cc)... (run: https://github.com/microsoft/AzureTRE/actions/runs/12486899525) |
|
PR test environment destroy complete (RG: rg-tref33f08cc) |
|
/test-extended 386ad33 |
|
🤖 pr-bot 🤖 🏃 Running extended tests: https://github.com/microsoft/AzureTRE/actions/runs/12487080630 (with refid (in response to this comment from @jonnyry) |
|
/test-destroy-env |
|
Destroying PR test environment (RG: rg-tref33f08cc)... (run: https://github.com/microsoft/AzureTRE/actions/runs/12492093469) |
|
PR test environment destroy complete (RG: rg-tref33f08cc) |
Resolves #4004
What is being addressed
Upgrade azurerm terrafom provider from v3.112.0 to v3.117.0.
An intermittent issue exists where deploying a TRE using the same name as a recently deleted TRE causes the deployment to fail due to DNS issues with storage accounts (see #4004). This has been resolved in azurerm terraform provider v3.113.0