You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
Current Terraform and Cloudflare provider version
Terraform: 1.5.2
Provider: 4.18.0
Description
We are attempting to create a
cloudflare_tunnel
and correspondingcloudflare_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 acloudflare_tunnel_config
resource per documentation here. Creating a tunnel config with this parameter causeswarp_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 accompanyingcloudflare_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
References
No response
The text was updated successfully, but these errors were encountered: