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

Ability to create cloudflare_tunnel_config with warp_routing enabled. #2916

Closed
dmitriydvoryanchuk-chime opened this issue Nov 7, 2023 · 2 comments
Labels
triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@dmitriydvoryanchuk-chime
Copy link

dmitriydvoryanchuk-chime commented Nov 7, 2023

Current Terraform and Cloudflare provider version

Terraform: 1.5.2
Provider: 4.18.0

Description

We are attempting to create a cloudflare_tunnel and corresponding cloudflare_tunnel_config to allow our WARP clients access to private networks specified in the routes for that tunnel. When the tunnel is created in the UI/dashboard, it is automatically configured as:

"config": { "warp-routing": { "enabled": true } }, "source": "cloudflare"

However, the provider is expecting an ingress_rule block as required when creating a cloudflare_tunnel_config resource per documentation here. Creating a tunnel config with this parameter causes warp_routing config to flip to false, which would break connectivity.

Running an import only imports the above config: ingress_rule is ignored.

This also means we can't create a cloudflare_tunnel resource, because without the accompanying cloudflare_tunnel_config resource, warp_routing is also set as false by default.

Use cases

The use case is being able to manage WARP-enabled cloudfalred tunnel resources via TF.

Potential Terraform configuration

resource "cloudflare_tunnel_config" "aws_vpc_it_prod" {
  account_id = "id"
  tunnel_id  = cloudflare_tunnel.aws_vpc_it_prod.id
  config {
    warp_routing {
      enabled = true
    }
}

References

No response

@dmitriydvoryanchuk-chime dmitriydvoryanchuk-chime added kind/enhancement Categorizes issue or PR as related to improving an existing feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 7, 2023
Copy link
Contributor

github-actions bot commented Nov 7, 2023

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.

@jacobbednarz
Copy link
Member

this seems to be a bug; can you please open a bug issue with the requested information to have this triaged by the service team?

@jacobbednarz jacobbednarz closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2023
@jacobbednarz jacobbednarz added triage/unresolved Indicates an issue that can not or will not be resolved. and removed kind/enhancement Categorizes issue or PR as related to improving an existing feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

2 participants