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

azurerm_key_vault - Virtual Network Rules not working with multiple subnet id's #2129

Closed
virtualbubble opened this issue Oct 22, 2018 · 3 comments · Fixed by #2324
Closed
Labels
Milestone

Comments

@virtualbubble
Copy link

azurerm_key_vault - support for Virtual Network Rules (#2027) not working with multiple subnet id's

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 Version

0.11.9

Affected Resource(s)

  • azurerm_key_vault

Terraform Configuration Files

resource "azurerm_resource_group" "test" {
  name     = "keyvault-testvault-rg01"
  location = "westeurope"
}

resource "azurerm_key_vault" "test" {
  name                        = "keyvault-we-test-key01"
  location                    = "${azurerm_resource_group.test.location}"
  resource_group_name         = "${azurerm_resource_group.test.name}"
  enabled_for_disk_encryption = true
  tenant_id                   = "<TENANT_ID>"

  sku {
    name = "standard"
  }

  network_acls {
    default_action             = "Deny"
    bypass                     = "AzureServices"
    virtual_network_subnet_ids = ["<SUBNET_ID_1>","<SUBNET_ID_2>"]
  }

  tags {
    environment = "tEST"
  }
}

provider "azurerm" {
  subscription_id = "${var.subscription_id}"
  client_id       = "${var.client_id}"
  client_secret   = "${var.client_secret}"
  tenant_id       = "${var.tenant_id}"
}


variable "subscription_id" {}
variable "client_id" {}
variable "client_secret" {}
variable "tenant_id" {}

Debug Output

Resources do not build at all. Continues for over an hour.

Panic Output

Expected Behavior

Build key vault and add muliple subnet id's

Actual Behavior

Keyvault does not build when supplying more than one subnet id

Steps to Reproduce

  1. terraform apply

Important Factoids

Keyvault does not build when supplying more than one subnet id . Copy the code above to test and test with one subnet id and then destroy and add an additional subnet id and test.

References

-->

  • #0000
@bpoland
Copy link

bpoland commented Oct 26, 2018

I am seeing the same thing -- it works fine with one subnet ID but when you add a second one, it gets stuck in "Still creating..." forever. I have enabled trace logging but nothing useful seems to be in there.

@rhollins
Copy link

rhollins commented Oct 29, 2018

I have the exactly same issue

Terraform v0.11.10

  • provider.azurerm v1.17.0

@ghost
Copy link

ghost commented Mar 5, 2019

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 Mar 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants