Open ccsandhanshive opened 2 years ago
Thanks for raising this issue. Though the firewall rule is created, but actually the server cannot be accessed with that IP. This issue will be fixed at service side since the expected behavior should fail as you mentioned. So filed an issue on https://github.com/Azure/azure-rest-api-specs/issues/20616 for tracking.
Is there an existing issue for this?
Community Note
Terraform Version
1.0.0
AzureRM Provider Version
3.2.0
Affected Resource(s)/Data Source(s)
azurerm_postgresql_flexible_server_firewall_rule
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform should not allow creation of azurerm_postgresql_flexible_server_firewall_rule resource in private access of postgresql flexible server rather it should throw a validation error saying postgresql flexible server firewall rule resource can be created only where public access is allowed
Actual Behaviour
azurerm_postgresql_flexible_server_firewall_rule
successfully where Private access (VNet Integration) is allowed in postgresql flexible serverSteps to Reproduce
terraform apply
Important Factoids
No response
References