Open jcetina opened 17 hours ago
Hi @jcetina Have you tried to reproduce it using the latest azurerm provider? as of today is 4.7.0
@Chambras I have not. I'm happy to try it, but also I'm not sure even if it works that it solves my or other Azure customer's problems. Rolling forward a full version from 3->4 is non-trivial at scale. I guess what I'm saying is that if it works in 4, can you backport it to 3?
Is there an existing issue for this?
Community Note
Terraform Version
1.8.1
AzureRM Provider Version
3.116.0
Affected Resource(s)/Data Source(s)
azurerm_subnet
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The expected behavior is for Terraform to simply update the existing resource without replacement. The Azure rest API allows for modification of this setting without replacement. I will also add that the current behavior of this module makes adopting this setting for existing subnets with large amounts of resources on them extremely challenging.
Actual Behaviour
As seen in the plan, terraform wants to replace the subnet specifically because of the change of
default_outbound_access_enabled
from true to false.Steps to Reproduce
Create a subnet with
default_outbound_access_enabled
set to true, deploy it, and then switch it to false and run a plan.Important Factoids
No response
References
No response