-
Notifications
You must be signed in to change notification settings - Fork 626
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_ruleset causing crash #4560
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Thank you for opening this issue and sorry to hear you're hitting issues. Unfortunately, the reproduction case provided contains HCL dynamic expressions. Examples of these are:
Maintainers don't accept these as reproduction cases since using these constructs and expressions can hold their own logic bugs which are outside of the provider and not able to be diagnosed. For maintainers to triage this issue, we recommend providing a minimal reproduction test case that is only contains the impacted resources and can be easily reproduced in an isolated environment. Without providing this, maintainers are limited in what support they can provide. |
Sorry for the delay, but I can confirm this is happening for me without the conditional as well. |
running this without conditionals is working expected for me. HCL
Apply + plan
you'll either need to find what has gone wrong in your state or track down what differs here for the repro as it looks to isolated to your setup. |
Confirmation
Terraform and Cloudflare provider version
Affected resource(s)
Terraform configuration files
Link to debug output
https://gist.github.com/arunesh90/63af12b26e8546d5f783fa24442ef7dc
Panic output
Expected output
One of our cache rules got recently manually changed on the dashboard while it's managed by the config above, so the expectation from this new plan would be to sync it back up or at least give some kind of error/warning about it - Instead it appears that something inside the ruleset code of the provider crashed.
The exact rule that got changed is the
Homepage cache
one from my config.On the dashboard we simply added another hostname, so it's now:
versus what's in the config:
Seems as if the ruleset code had issues handling that manual change and couldn't generate a change for that and proceeded to crash.
Actual output
Provider should've created a change for my ruleset that got manually edited, but instead it crashed.
Steps to reproduce
Homepage cache
one from my config, via TerraformAdditional factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: