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

Two cloudflare_tunnel_config's do only create one resource and overwrite each other on every apply #3228

Closed
2 tasks done
mrclrchtr opened this issue Apr 4, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@mrclrchtr
Copy link

mrclrchtr commented Apr 4, 2024

Confirmation

  • My issue isn't already found on the issue tracker.
  • I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.7.5
on darwin_arm64

  • provider registry.terraform.io/cloudflare/cloudflare v4.29.0

Affected resource(s)

cloudflare_tunnel_config

Terraform configuration files

resource "cloudflare_tunnel_config" "prod" {
  account_id = cloudflare_account.this.id
  tunnel_id  = cloudflare_tunnel.this.id

  config {
    warp_routing {
      enabled = true
    }
    ingress_rule {
      hostname = "${local.environments.prod.subdomain}.${local.environments.prod.domain}"
      service  = local.environments.prod.service
      origin_request {
        access {
          required  = true
          team_name = "teamname"
          aud_tag = [
            cloudflare_access_application.this[local.environments.prod.name].aud
          ]
        }
      }
    }
    ingress_rule {
      service = "http_status:404"
    }
  }
}

resource "cloudflare_tunnel_config" "test" {
  account_id = cloudflare_account.this.id
  tunnel_id  = cloudflare_tunnel.this.id

  config {
    warp_routing {
      enabled = true
    }
    ingress_rule {
      hostname = "${local.environments.test.subdomain}.${local.environments.test.domain}"
      service  = local.environments.test.service
      origin_request {
        access {
          required  = true
          team_name = "teamname"
          aud_tag = [
            cloudflare_access_application.this[local.environments.prod.name].aud
          ]
        }
      }
    }
    ingress_rule {
      service = "http_status:404"
    }
  }
}

Link to debug output

N/A

Panic output

No response

Expected output

Two resources should be created.

Actual output

One Resource is created.

Steps to reproduce

Crate two resources and apply

Additional factoids

No response

References

No response

@mrclrchtr mrclrchtr added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 4, 2024
Copy link
Contributor

github-actions bot commented Apr 4, 2024

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

@github-actions github-actions bot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 4, 2024
Copy link
Contributor

github-actions bot commented Apr 4, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@Cyb3r-Jak3
Copy link
Contributor

Each tunnel can only have a single configuration. You will need to make a second tunnel for the test tunnel.

@mrclrchtr
Copy link
Author

You are right. I was thinking wrong. I need to dynamically add multiple ingress_rules per environment. Then I can use one tunnel. Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants