terraform-provider-azurerm: Private Link Endpoint resource doesn't accept DNS Alias

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

v0.12.20

Affected Resource(s)

  • azurerm_private_endpoint

Terraform Configuration Files

resource "azurerm_private_endpoint" "example" {
  name                = "ExampleName"
  location            = var.location
  resource_group_name = local.resource_group_name
  subnet_id           = azurerm_subnet.subnetname.id

  private_service_connection {
    name                              = "ToEndpoint"
    is_manual_connection              = true
    private_connection_resource_id      = "uniquednsname.eastus.azure.privatelinkservice"
    request_message                   = "Customer # XXXX"

  }
}

Expected Behavior

Azure supports either the resource ID or the DNS name to reference the private link service. I expected to be able to provide the DNS FQDN as the “private_connection_resource_id” or have an option to pass a “private_connection_alias” or similar.

Actual Behavior

Terraform returned an error that it was an invalid URI for the request.

Steps to Reproduce

  1. terraform apply

Important Factoids

References

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 20
  • Comments: 18

Most upvoted comments

As of the latest release of the provider (v 2.55.0 ), you should be able to use the private_connection_resource_alias property instead of the private_connection_resource_id property to achieve this.

Hi @WodansSon ,

Any news about updating the PE API to 2019-11-01 (or newer?)? I see there are couple of issues about the need to update the API, this included. We are currently hitting this one, as we try to create PE to Snowflake DB. Is there already some work started on this in some branch or something? 😃

Answering my own question - apparently, when using private_connection_resource_alias, the is_manual_connection flag has to be set to true. Also, request_message cannot be empty.

Any ETA would be appreciated!

Is it just snowflake users who are seeing this issue? (myself included) Is there an ETA for the API upgrade?