Exposed ignore_missing_vnet_service_endpoint attribute #2056
Conversation
| @@ -84,7 +85,7 @@ The following arguments are supported: | |||
|
|
|||
| * `subnet_id` - (Required) The ID of the subnet that the PostgreSQL server will be connected to. | |||
|
|
|||
| ~> **NOTE:** Due to [a bug in the Azure API](https://github.com/Azure/azure-rest-api-specs/issues/3719) this resource currently doesn't expose the `ignore_missing_vnet_service_endpoint` field and defaults this to `false`. Terraform will check during the provisioning of the Virtual Network Rule that the Subnet contains the Service Rule to verify that the Virtual Network Rule can be created. | |||
| * `ignore_missing_vnet_service_endpoint` - (Optional) Create the virtual network rule before the subnet has the virtual network service endpoint enabled. The default value is false. | |||
There was a problem hiding this comment.
Create the virtual network rule before the subnet has the virtual network service endpoint enabled. The default value is false.
I think we could phrase this better to match the syntax of the other fields:
Should the Virtual Network Rule be created before the Subnet has the Virtual Network Service Endpoint enabled? Defaults to `false`
There was a problem hiding this comment.
How about I copy it from the API docs directly?
Create firewall rule before the virtual network has vnet service endpoint enabled.
There was a problem hiding this comment.
Sure - but we should still match the language used across the other resources, which prefixes things with Should [xxx] be applied/enabled etc?
|
|
|
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
Fixed the issue for the ignore_missing_vnet_service_endpoint attribute, turns out it's an async operation for Postgre SQL. Currently have many customers asking for this functionality.