Skip to content
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

Subnets with multiple addressPrefixes cannot be used as a source or created #5140

Closed
smarterclayton opened this issue Dec 12, 2019 · 3 comments · Fixed by #6493
Closed

Subnets with multiple addressPrefixes cannot be used as a source or created #5140

smarterclayton opened this issue Dec 12, 2019 · 3 comments · Fixed by #6493

Comments

@smarterclayton
Copy link
Contributor

smarterclayton commented Dec 12, 2019

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

7427e8c

Affected Resource(s)

  • azurerm_subnet

Terraform Configuration Files

data "azurerm_subnet" "preexisting_worker_subnet" {
  count = var.preexisting_network ? 1 : 0

  resource_group_name  = var.network_resource_group_name
  virtual_network_name = var.virtual_network_name
  name                 = var.worker_subnet
}

locals {
  # empty when subnet has multiple addressPrefixes (2+)
  address_prefix data.azurerm_subnet.preexisting_worker_subnet[0].address_prefix
}

Expected Behavior

  • Retrieve address_prefixes when multiple are set on the subnet
  • Allow creation of subnets with 2+ address_prefixes (ipv4 and ipv6, for example)

Actual Behavior

Nil data on retrieval, unable to create with existing API

@sigv
Copy link
Contributor

sigv commented Jan 17, 2020

For completeness sake in this ticket: The response to /subscriptions/guid/resourceGroups/name/providers/Microsoft.Network/virtualNetworks/vnet/subnets/subnet has a properties.subnets array where each object has properties.addressPrefix string, which gets replaced by a properties.addressPrefixes array of strings. This seems to be already getting worked on in #5139 though.

@ghost
Copy link

ghost commented May 1, 2020

This has been released in version 2.8.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.8.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented May 28, 2020

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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.