Bug #17930 was closed without solution by bot: virtual_network_subnet_id is always reset when connecting to virtual network using azurerm_app_service_virtual_network_swift_connection

[arne21a]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

v1.4.6 on linux_arm64

AzureRM Provider Version

3.75.0

Affected Resource(s)/Data Source(s)

azurerm_app_service_virtual_network_swift_connection

Terraform Configuration Files

See: [virtual_network_subnet_id is always reset when connecting to virtual network using azurerm_app_service_virtual_network_swift_connection](https://github.com/hashicorp/terraform-provider-azurerm/issues/17930)

Debug Output/Panic Output

See: [virtual_network_subnet_id is always reset when connecting to virtual network using azurerm_app_service_virtual_network_swift_connection](https://github.com/hashicorp/terraform-provider-azurerm/issues/17930)

Expected Behaviour

The bug virtual_network_subnet_id is always reset when connecting to virtual network using azurerm_app_service_virtual_network_swift_connection was closed by a bot without a solution.
This issue persists and has many upvotes. Please reopen.

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[tombuildsstuff]

@arne21a as explained in this comment there isn't a bug here - you need to use ignore_changes to ignore this field when using the separate azurerm_app_service_virtual_network_swift_connection resource.

Since this is a configuration question rather than a bug in the Provider I'm going to close this issue - but as mentioned in the linked comment above, and in the documentation - you need to either define this field inline and not use the azurerm_app_service_virtual_network_swift_connection resource - or use ignore_changes on this field when using the azurerm_app_service_virtual_network_swift_connection resource.

Thanks!

[arne21a]

Thank you for your quick answer, but i fear that I feel similar to the reactions on the suggested answer. The current behaviour was an issue for multiple people and continues to be one.

The current implementation of the CAF supermodule by microsoft is also affected.
See: aztfmod/terraform-azurerm-caf#1975
Adding a lifecycle policy prevents us from removing or changing the value after creation.

To me this issue looks similar to this one: #24681

If there are attributes which can be managed from somewhere else like azure policy or other terraform resources, there needs to be an option to conditionally ignore changes. Not being able to do this will result in issues when terraform is part of a bigger solution.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.