Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadence to ensure its stability and reliability, including the v5.9 release. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach – we will be focusing on specific resources for every release, stabilizing the release, and closing all associated bugs with that resource before moving onto resolving migration issues.
Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.
This release includes a new resource, cloudflare_snippet, which replaces cloudflare_snippets. cloudflare_snippet is now considered deprecated but can still be used. Please utilize cloudflare_snippet as soon as possible.
Changes
- Resources stabilized:
cloudfare_zone_settingcloudflare_worker_scriptcloudflare_worker_routetiered_cache
- NEW resource
cloudflare_snippetwhich should be used in place ofcloudflare_snippets.cloudflare_snippetsis now deprecated. This enables the management of Cloudflare’s snippet functionality through Terraform. - DNS Record Improvements: Enhanced handling of DNS record drift detection
- Load Balancer Fixes: Resolved
created_onfield inconsistencies and improved pool configuration handling - Bot Management: Enhanced auto-update model state consistency and fight mode configurations
- Other bug fixes
For a more detailed look at all of the changes, refer to the changelog in GitHub.
Issues Closed
- #5921: In cloudflare_ruleset removing an existing rule causes recreation of later rules
- #5904: cloudflare_zero_trust_access_application is not idempotent
- #5898: (cloudflare_workers_script) Durable Object migrations not applied
- #5892: cloudflare_workers_script secret_text environment variable gets replaced on every deploy
- #5891: cloudflare_zone suddenly started showing drift
- #5882: cloudflare_zero_trust_list always marked for change due to read only attributes
- #5879: cloudflare_zero_trust_gateway_certificate unable to manage resource (cant mark as active/inactive)
- #5858: cloudflare_dns_records is always updated in-place
- #5839: Recurring change on cloudflare_zero_trust_gateway_policy after upgrade to V5 provider & also setting expiration fails
- #5811: Reusable policies are imported as inline type for cloudflare_zero_trust_access_application
- #5795: cloudflare_zone_setting inconsistent value of “editable” upon apply
- #5789: Pagination issue fetching all policies in “cloudflare_zero_trust_access_policies” data source
- #5770: cloudflare_zero_trust_access_application type warp diff on every apply
- #5765: V5 / cloudflare_zone_dnssec fails with HTTP/400 “Malformed request body”
- #5755: Unable to manage Cloudflare managed WAF rules via Terraform
- #5738: v4 to v5 upgrade failing Error: no schema available AND Unable to Read Previously Saved State for UpgradeResourceState
- #5727: cloudflare_ruleset http_request_cache_settings bypass mismatch between dashboard and terraform
- #5700: cloudflare_account_member invalid type ‘string’ for field ‘roles’
If you have an unaddressed issue with the provider, we encourage you to check the open issues and open a new issue if one does not already exist for what you are experiencing.
Upgrading
We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized.
If you’d like more information on migrating from v4 to v5, please make use of the migration guide. We have provided automated migration scripts using Grit which simplify the transition. These do not support implementations which use Terraform modules, so customers making use of modules need to migrate manually. Please make use of terraform plan to test
your changes before applying, and let us know if you encounter any additional issues by reporting to our GitHub repository.
For more info
Source: Cloudflare
