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

Network ordering is always set to zero #95

Closed
itakouna opened this issue Nov 2, 2020 · 0 comments · Fixed by #96
Closed

Network ordering is always set to zero #95

itakouna opened this issue Nov 2, 2020 · 0 comments · Fixed by #96

Comments

@itakouna
Copy link
Contributor

itakouna commented Nov 2, 2020

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

v1.6.3

Affected Resource(s)

  • servers' network

Expected Behavior

The network should be added based on defined order in the TF file

Actual Behavior

The network ordering defined order in the TF file is ignored

Steps to Reproduce

create a server with two network interfaces

resource "gridscale_server" "node" {
.......

  network {
    object_uuid = data.gridscale_public_network.public.id
  }
network {
    object_uuid = gridscale_network.private.id
  }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant