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

crusoe_vpc_firewall_rule name should be dynamic with prefix #1

Open
st0ked622 opened this issue May 18, 2024 · 0 comments
Open

crusoe_vpc_firewall_rule name should be dynamic with prefix #1

st0ked622 opened this issue May 18, 2024 · 0 comments

Comments

@st0ked622
Copy link

st0ked622 commented May 18, 2024

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

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

1 participant