You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, azurerm_app_service does not support adding such a hybrid connection.
It is pretty annoying, adding the hybrid connection manualy after a deployment.
Hybrid connections could be created manualy in a seperate resource group and can be referenced by name and/without namespace (depends on implementation) in the app service.
New or Affected Resource(s)
azurerm_app_service
Potential Terraform Configuration
resource"azurerm_app_service""webapp" {
name ="name"
resource_group_name ="rg_name"
location ="West US 2"
app_service_plan_id = azurerm_app_service_plan.sp.id.
.
.
networking {
hybrid_connection {
name ="hybrid_connection_name_example"
namespace ="namespace_example"
}
hybrid_connection {
name ="hybrid_connection_name_example2"
namespace ="namespace_example2"
}
}
}
The text was updated successfully, but these errors were encountered:
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.
Community Note
Description
Hybrid Connections are used to access endpoints and resources in an other network, as described in the documentation here.
Currently, azurerm_app_service does not support adding such a hybrid connection.
It is pretty annoying, adding the hybrid connection manualy after a deployment.
Hybrid connections could be created manualy in a seperate resource group and can be referenced by name and/without namespace (depends on implementation) in the app service.
New or Affected Resource(s)
azurerm_app_service
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: