-
Notifications
You must be signed in to change notification settings - Fork 632
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_load_balancer custom rules config drift not detected #4798
Comments
Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of This issue has been marked with |
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
This issue was closed because it has been stalled for 7 days with no activity. |
Confirmation
Terraform and Cloudflare provider version
Terraform v1.5.7
on darwin_arm64
Affected resource(s)
cloudflare_load_balancer
Terraform configuration files
Link to debug output
NA
Panic output
NA
Expected output
Terraform plan should be detecting the config drift when the rules are deleted from the loadbalancer after getting created.
Actual output
No changes. Your infrastructure matches the configuration.
Steps to reproduce
Additional factoids
Custom rules in 4.48 is mentioned as beta but bringing this observation if this issue not being tracked
Custom rules were deleted from Cloudflare portal (GUI) after they got created through this terraform config. Later when the same config is used to run the plan, it is not detecting this config drift to show those rules to be created again.
Other observation is that, terraform will detect the drift if at least one rule exist but does not work when all of the existing once deleted which got created through config and exist in terraform state
References
No response
The text was updated successfully, but these errors were encountered: