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

Firewall rules are added without using neither firewall_resource nor firewall_rule in network #100

Closed
itakouna opened this issue Nov 3, 2020 · 1 comment
Assignees

Comments

@itakouna
Copy link
Contributor

itakouna commented Nov 3, 2020

Terraform gridscale provider

v1.7.3

Affected Resource(s)

  • server_networks

Terraform Configuration Files

terraform {
  required_providers {
    gridscale = "~> 1.7.0"
  }
}

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" {
}

Expected Behavior

it should behave as in v1.6.3, so if there is no Firewall rules is defined, the default rules should not be added.

Actual Behavior

default firewall rules are added

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply #v1.7.3

  2. The API response with firewall rules

1: {create_time: "2020-11-03T14:19:57Z", vlan: null, l2security: true, vxlan: null,…}
bootdevice: false
create_time: "2020-11-03T14:19:57Z"
firewall: {,…}
rules-v4-in: [{order: 1, action: "accept", comment: "DHCP IPv4", dst_port: "67:68", protocol: "udp",…},…]
0: {order: 1, action: "accept", comment: "DHCP IPv4", dst_port: "67:68", protocol: "udp",…}
1: {order: 2, action: "accept", comment: "Highports TCP", dst_port: "32768:65535", protocol: "tcp",…}
2: {order: 3, action: "accept", comment: "Highports UDP", dst_port: "32768:65535", protocol: "udp",…}
3: {order: 4, action: "drop", comment: "Drop all other UDP", dst_port: "1:65535", protocol: "udp",…}
4: {order: 5, action: "drop", comment: "Drop all other TCP", dst_port: "1:65535", protocol: "tcp",…}
rules-v6-in: [{order: 1, action: "accept", comment: "DHCP IPv6", dst_port: "546:547", protocol: "udp",…},…]
0: {order: 1, action: "accept", comment: "DHCP IPv6", dst_port: "546:547", protocol: "udp",…}
1: {order: 2, action: "accept", comment: "Highports TCP", dst_port: "32768:65535", protocol: "tcp",…}
2: {order: 3, action: "accept", comment: "Highports UDP", dst_port: "32768:65535", protocol: "udp",…}
3: {order: 4, action: "drop", comment: "Drop all other UDP", dst_port: "1:65535", protocol: "udp",…}
4: {order: 5, action: "drop", comment: "Drop all other TCP", dst_port: "1:65535", protocol: "tcp",…}
firewall_template_uuid: null
l2security: true
l3security: []
mac: "3e:40:f7:3b:67:01"
mcast: null
network_type: "network"
network_uuid: "e196b077-8286-4164-84d7-662af768745c"
object_name: "Public Network"
object_uuid: "e196b077-8286-4164-84d7-662af768745c"
ordering: 0
partner_uuid: "95a2980b-7012-43dd-81f2-07577cfcb9f0"
public_net: true
server_uuid: "2fbef5b7-ac7a-448d-a699-5ee96322a8b5"
vlan: null
vxlan: null

from the expert panel

Screenshot 2020-11-03 at 15 28 59

Compared to gridscale provider v.1.6.3

Screenshot 2020-11-03 at 15 31 59

API

firewall: {}
@itakouna
Copy link
Contributor Author

itakouna commented Nov 4, 2020

solved in v1.7.4

@itakouna itakouna closed this as completed Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants