We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
all versiions
resource "gridscale_server" "node" { name = "network-ordering" cores = 1 memory = 2 network { object_uuid = data.gridscale_public_network.public.id } network { object_uuid = gridscale_network.private.id } } resource "gridscale_network" "private" { name = "network-ordering-private" } data "gridscale_public_network" "public" { }
The network ordering should be consistent and match network resource order as defined in the TF file
The network order is assigned randomly
Please list the steps required to reproduce the issue, for example: terraform plan
+ network { + bootdevice = (known after apply) + create_time = (known after apply) + mac = (known after apply) + network_type = (known after apply) + object_name = (known after apply) + object_uuid = "e196b077-8286-4164-84d7-662af768745c" + ordering = 0 } + network { + bootdevice = (known after apply) + create_time = (known after apply) + mac = (known after apply) + network_type = (known after apply) + object_name = (known after apply) + object_uuid = (known after apply) + ordering = 0 }
after running terraform apply, I run terraform plan again
terraform apply
terraform plan
terraform plan + network { + bootdevice = (known after apply) + create_time = (known after apply) + mac = (known after apply) + network_type = (known after apply) + object_name = (known after apply) + object_uuid = "e196b077-8286-4164-84d7-662af768745c" **+ ordering = 0** } - network { - bootdevice = false -> null - create_time = "2020-11-03 14:05:34 +0000 UTC" -> null - mac = "16:63:39:97:97:01" -> null - network_type = "network" -> null - object_name = "network-ordering-private" -> null - object_uuid = "1d5d7e68-d3b1-4506-8773-4b1e48be1e06" -> null **- ordering = 0 -> null** } + network { + bootdevice = false + create_time = "2020-11-03 14:05:34 +0000 UTC" + mac = "16:63:39:97:97:01" + network_type = "network" + object_name = "network-ordering-private" + object_uuid = "1d5d7e68-d3b1-4506-8773-4b1e48be1e06" **+ ordering = 0** } - network { - bootdevice = false -> null - create_time = "2020-11-03 14:05:37 +0000 UTC" -> null - mac = "16:63:39:97:97:02" -> null - network_type = "network" -> null - object_name = "Public Network" -> null - object_uuid = "e196b077-8286-4164-84d7-662af768745c" -> null **- ordering = 1 -> null** } The network order has changed
The text was updated successfully, but these errors were encountered:
solved in v1.7.4
Sorry, something went wrong.
nvthongswansea
No branches or pull requests
Terraform Version
all versiions
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The network ordering should be consistent and match network resource order as defined in the TF file
Actual Behavior
The network order is assigned randomly
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
+ network { + bootdevice = (known after apply) + create_time = (known after apply) + mac = (known after apply) + network_type = (known after apply) + object_name = (known after apply) + object_uuid = "e196b077-8286-4164-84d7-662af768745c" + ordering = 0 } + network { + bootdevice = (known after apply) + create_time = (known after apply) + mac = (known after apply) + network_type = (known after apply) + object_name = (known after apply) + object_uuid = (known after apply) + ordering = 0 }
after running
terraform apply
, I runterraform plan
againThe text was updated successfully, but these errors were encountered: