azurerm_network_interface: changing the ip_configuration property to no longer force new resource.

[neil-yechenwei]

Issue:
Terraform azurerm recreates network interface when the ip configuration is changed.
[fixes #2746]

Root cause:
The parameter "private_ip_address_version" under ip_configuration object is set to "ForceNew: true,", which causes that terraform destroy and create a new network interface when ip configuration is update.

Fix:
Remove the attribute "ForceNew: true,". Then terraform will just update ip configuration settings under network interface after updated ip configuration.

[WodansSon]

Neil, the LGTM... I would like a couple of changes added before we push this.

• Add a test case for this configuration, as it should be supported since you can do this via portal
• Update the documentation to reflect the new behavior

[WodansSon]

Taking a closer look at this and thinking about it a bit more, neither of my requested actions are required...

• There is already a test case that adds multiple ip configurations
• There is nothing to document because this is the expected behavior.

[WodansSon]

Thanks @neil-yechenwei the LGTM! 🚀

[WodansSon]

[ghost]

This has been released in version 1.34.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.34.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!