Terraform v5.8.2 available with resource stabilization improvements

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 cadeance to ensure it's stability and reliability. 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.

Changes

• Resources stabilized:
  • cloudflare_custom_pages
  • cloudflare_page_rule
  • cloudflare_dns_record
  • cloudflare_argo_tiered_caching
• Addressed chronic drift issues in cloudflare_logpush_job, cloudflare_zero_trust_dns_location, cloudflare_ruleset & cloudflare_api_token
• cloudflare_zone_subscription returns expected values rate_plan.id from former versions
• cloudflare_workers_script can now successfully be destroyed with bindings & migration for Durable Objects now recorded in tfstate
• Ability to configure add_headers under cloudflare_zero_trust_gateway_policy
• Other bug fixes

For a more detailed look at all of the changes, see the changelog ↗ in GitHub.

Issues Closed

• #5666: cloudflare_ruleset example lists id which is a read-only field ↗
• #5578: cloudflare_logpush_job plan always suggests changes ↗
• #5552: 5.4.0: Since provider update, existing cloudflare_list_item would be recreated "created" state ↗
• #5670: cloudflare_zone_subscription: uses wrong ID field in Read/Update ↗
• #5548: cloudflare_api_token resource always shows changes (drift) ↗
• #5634: cloudflare_workers_script with bindings fails to be destroyed ↗
• #5616: cloudflare_workers_script Unable to deploy worker assets ↗
• #5331: cloudflare_workers_script 500 internal server error when uploading python ↗
• #5701: cloudflare_workers_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions ↗
• #5704: cloudflare_workers_script randomly fails to deploy when changing compatibility_date ↗
• #5439: cloudflare_workers_script (v5.2.0) ignoring content and bindings properties ↗
• #5522: cloudflare_workers_script always detects changes after apply ↗
• #5693: cloudflare_zero_trust_access_identity_provider gives recurring change on OTP pin login ↗
• #5567: cloudflare_r2_custom_domain doesn't roundtrip jurisdiction properly ↗
• #5179: Bad request with when creating cloudflare_api_shield_schema resource ↗

If you have an unaddressed issue with the provider, we encourage you to check the open issues ↗ and open a new one 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, although 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

• Terraform provider ↗
• Documentation on using Terraform with Cloudflare