Skip to content

crusoe_vpc_firewall_rule name should be dynamic with prefix #1

Open
@st0ked622

Description

@st0ked622

If multiple instances of this repo are used in the same environment for testing, the hardcoded name does not provide the flexibility to deploy multiple copies.

Original
resource "crusoe_vpc_firewall_rule" "rke_rule" {
network = local.ingress_interface.network
name = "rke-pub-access"
action = "allow"
direction = "ingress"
protocols = "tcp"
source = "0.0.0.0/0"
source_ports = "1-65535"
destination = "${local.ingress_interface.private_ipv4.address}/32"
destination_ports = "6443"
}

Updated:
resource "crusoe_vpc_firewall_rule" "rke_rule" {
network = local.ingress_interface.network
name = "${var.instance_name_prefix}-rke-pub-access"
action = "allow"
direction = "ingress"
protocols = "tcp"
source = "0.0.0.0/0"
source_ports = "1-65535"
destination = "${local.ingress_interface.private_ipv4.address}/32"
destination_ports = "6443"
}

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @st0ked622

        Issue actions

          crusoe_vpc_firewall_rule name should be dynamic with prefix · Issue #1 · crusoecloud/crusoe-ml-rke2