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_network_interface does not maintain the order of the dns_servers list #3298

Closed
raphaelcardoso opened this issue Apr 23, 2019 · 3 comments · Fixed by #5784
Closed

Comments

@raphaelcardoso
Copy link

raphaelcardoso commented Apr 23, 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

Terraform v0.11.13

  • provider.azurerm v1.25.0

Affected Resource(s)

  • azurerm_network_interface

Terraform Configuration Files

resource "azurerm_network_interface" "this" {
  name                = "${var.vm_name}-nic"
  location            = "${azurerm_resource_group.this.location}"
  resource_group_name = "${azurerm_resource_group.this.name}"

  dns_servers = [
    "10.0.0.5",
    "10.0.0.6",
    "172.27.0.5"
  ]

  ip_configuration {
    name      = "ipconfig1"
    subnet_id = "${data.azurerm_subnet.this.id}"

    private_ip_address_allocation = "Static"
    private_ip_address            = "172.27.1.10"
  }
}

Debug Output

Panic Output

Expected Behavior

Fragment from the terraform.tfstate file, containing sequential numbers that rule the order.

"primary": {
	"id": "/subscriptions/...",
	"attributes": {
		"applied_dns_servers.#": "3",
		"applied_dns_servers.0": "10.0.0.5",
		"applied_dns_servers.1": "10.0.0.6",
		"applied_dns_servers.2": "172.27.0.5",
		"dns_servers.#": "3",
		"dns_servers.0": "10.0.0.5",
		"dns_servers.1": "10.0.0.6",
		"dns_servers.2": "172.27.0.5",
		"...": "...",
	},
	"meta": {},
	"tainted": false
},

Actual Behavior

Fragment from the terraform.tfstate file, containing random numbers that rule the order.

"primary": {
	"id": "/subscriptions/...",
	"attributes": {
		"applied_dns_servers.#": "3",
		"applied_dns_servers.2028884304": "10.0.0.6",
		"applied_dns_servers.3210460864": "172.27.0.5",
		"applied_dns_servers.3790012650": "10.0.0.5",
		"dns_servers.#": "3",
		"dns_servers.2028884304": "10.0.0.6",
		"dns_servers.3210460864": "172.27.0.5",
		"dns_servers.3790012650": "10.0.0.5",
		"...": "...",
	},
	"meta": {},
	"tainted": false
},

Steps to Reproduce

  1. terraform apply
@odee30

This comment has been minimized.

@ghost
Copy link

ghost commented Feb 24, 2020

This has been released in version 2.0.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.0.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 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 👉 hashibot-feedback@hashicorp.com. Thanks!

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