-
Notifications
You must be signed in to change notification settings - Fork 640
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
Cloudflare Tunnel warp_routing issues - plan need to be applied twice #2233
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Terraform debug log detected ✅ |
I have updated the TF_LOG to point to a full Terraform run. |
this issue is related to sending zero values in Terraform where it cannot differentiate the two in state (hence two runs fix it). i don't have an ETA on this but we have a larger body of work that is tracking zero values across the provider and i'll note this one against that. |
Since Cloudflare Enterprise Support redirect to this issue could we have any update please. Thanks. |
Do you happen to have any news on this one? |
This is no longer an issue and can be closed. It has been addressed within the Cloudflare Tunnel's API service. |
Confirmation
Terraform and Cloudflare provider version
registry.terraform.io/cloudflare/cloudflare v3.34.0
Affected resource(s)
cloudflare_tunnel_config
Terraform configuration files
Link to debug output
https://gist.github.com/calderonth/1eeed1c19592b9c2955bba78d661adf7
Panic output
No response
Expected output
The plan/apply should correctly set the warp_routing values on the first pass.
It sends an empty JSON structure on the first pass which results results in a broken configuration (no data routed throught the tunnel).
Running a second time the apply actually fills out the the warp_routing structure and the tunnel configuration is set accordingly.
Actual output
The plan shows it has applied successfully on the first apply when it hasn't.
Steps to reproduce
Additional factoids
I have also tried to remove the warp_routing section as it is supposed to be optional but that also results in an unusable tunnel when created from TF.
References
No response
The text was updated successfully, but these errors were encountered: