-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Associate Application Group to Private Endpoint on Bot Service #23414
Comments
I am also experiencing this issue, with exactly the same resource "azurerm_application_security_group" "bot_asg" {
name = "${module.naming.standard["application-security-group"]}-bot"
location = var.location
resource_group_name = var.resource_group_name
tags = var.tags
}
resource "azurerm_private_endpoint_application_security_group_association" "bot_pe_asg_association" {
private_endpoint_id = azurerm_private_endpoint.bot_pe.id
application_security_group_id = azurerm_application_security_group.bot_asg.id
} I'm on AzureRM version 3.72.0 and Terraform CLI v1.5.6. |
Any update on this? |
I am also experiencing this issue with azurerm provider version 3.82.0, terraform 1.6.4 |
I have the same issue. Is this the issue of terraform or azure? |
Any updates on this? I am also getting: |
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.74.0
Affected Resource(s)/Data Source(s)
azurerm_private_endpoint_application_security_group_association
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Application Security Group created and associated to private endpoint without errors.
Actual Behaviour
The Application Security Group is created and it's associated to private endpoint (This is private endpoint for bot Service), but the terraform gives that error (The work was done).
When try again, i got error saying the association already exists (it's true)
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: