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
The name provided in the private_service_connection block is not respected when creating the privateEndpointConnections.
I created the private endpoint with private_service_connection block as following:
Hi there and thank you for reporting this. I can't reproduce this to be honest. Did you try approving the connection? Potentially the name would be set after the approval? I have a ton of these all over the place, and name is set properly everywhere.
I get that the name might be set post approval, but what I am trying to do here is that I am trying to approve the private endpoints programatically. Ideally, if I am providing a name to an endpoint or a private_service_connection, it should be reflected in the resource and not wait for an approval. @favoretti
Is there an existing issue for this?
Community Note
The name provided in the private_service_connection block is not respected when creating the privateEndpointConnections.
I created the private endpoint with private_service_connection block as following:
location = var.location name = var.eventhub_pep_name resource_group_name = var.rg_name subnet_id = var.eventhub_subnet_id private_service_connection { is_manual_connection = true name = var.eventhub_pep_psc_name private_connection_resource_id = azurerm_eventhub_namespace.eventhub_namespace.id request_message = "Please approve" subresource_names = ["namespace"] } }
but when I do
I get some random string in the privateEndpointConnection's name field.
Terraform Version
1.6.4
AzureRM Provider Version
3.80.0
Affected Resource(s)/Data Source(s)
azurerm_private_endpoint
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
name to have value var.eventhub_pep_psc_name
Actual Behaviour
name has random string in the privateEndpointConnection
Steps to Reproduce
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: