---
title: Docs collections Changelog
image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

Docs collections

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

Jul 14, 2025
1. ### [Terraform v5.7.0 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-07-11-terraform-v570-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release, with 13.5% of resources impacted. We have committed to releasing improvements on a 2 week cadeance to ensure it's stability and relability, including the v5.7 release.  
Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases.  
#### Changes

  * Addressed permanent diff bug on Cloudflare Tunnel config
  * State is now saved correctly for Zero Trust Access applications
  * Exact match is now working as expected within `data.cloudflare_zero_trust_access_applications`
  * `cloudflare_zero_trust_access_policy` now supports OIDC claims & diff issues resolved
  * Self hosted applications with private IPs no longer require a public domain for `cloudflare_zero_trust_access_application`.
  * New resource:  
    * `cloudflare_zero_trust_tunnel_warp_connector`
  * Other bug fixes  
For a more detailed look at all of the changes, see the [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.7.0) in GitHub.  
#### Issues Closed

  * [#5563: cloudflare\_logpull\_retention is missing import ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5563)
  * [#5608: cloudflare\_zero\_trust\_access\_policy in 5.5.0 provider gives error upon apply unexpected new value: .app\_count: was cty.NumberIntVal(0), but now cty.NumberIntVal(1) ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5608)
  * [#5612: data.cloudflare\_zero\_trust\_access\_applications does not exact match ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5612)
  * [#5532: cloudflare\_zero\_trust\_access\_identity\_provider detects changes on every plan ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5532)
  * [#5662: cloudflare\_zero\_trust\_access\_policy does not support OIDC claims ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5662)
  * [#5565: Running Terraform with the cloudflare\_zero\_trust\_access\_policy resource results in updates on every apply, even when no changes are made - breaks idempotency ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5565)
  * [#5529: cloudflare\_zero\_trust\_access\_application: self hosted applications with private ips require public domain  ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5529)  
If you have an unaddressed issue with the provider, we encourage you to check the [open issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.  
#### Upgrading  
We suggest holding on migration to v5 while we work on stabilization of the v5 provider. This will ensure Cloudflare can work ahead and avoid any blocking issues.  
If you'd like more information on migrating from v4 to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). 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 ↗](https://github.com/cloudflare/terraform-provider-cloudflare).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)

Jun 23, 2025
1. ### [Cloudflare User Groups & SCIM User Groups are now in GA](https://edgetunnel-b2h.pages.dev/changelog/post/2025-06-23-user-groups-ga/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)  
We're announcing the GA of **User Groups for Cloudflare Dashboard** and **System for Cross Domain Identity Management (SCIM) User Groups**, strengthening our RBAC capabilities with stable, production-ready primitives for managing access at scale.

**What's New**

**User Groups \[GA\]**: [User Groups](https://edgetunnel-b2h.pages.dev/fundamentals/manage-members/user-groups/) are a new Cloudflare IAM primitive that enable administrators to create collections of account members that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group inheriting all permissions granted to the User Group. User Groups can be created manually or via our APIs.

**SCIM User Groups \[GA\]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.

**Stability & Scale**: These features have undergone extensive testing during the Public Beta period and are now ready for production use across enterprises of all sizes.  
Note  
SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are now officially deprecated as of June 2, 2025\. SCIM Virtual Groups end-of-life will take effect on December 2, 2025\. We strongly recommend migrating to SCIM User Groups to ensure continued support for SCIM synchronization to the Cloudflare Dashboard. If you haven’t used Virtual Groups, no action is required.  
For more info:

  * [Get started with User Groups](https://edgetunnel-b2h.pages.dev/fundamentals/manage-members/user-groups/)
  * [Explore our SCIM integration guide](https://edgetunnel-b2h.pages.dev/fundamentals/account/account-security/scim-setup/)

Jun 17, 2025
1. ### [Terraform v5.6.0 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-06-17-terraform-v560-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare)reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.6.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases.  
#### Changes

  * Broad fixes across resources with recurring diffs, including, but not limited to:  
    * `cloudflare_zero_trust_access_identity_provider`  
      * `cloudflare_zone`
  * `cloudflare_page_rules` runtime panic when setting `cache_level` to `cache_ttl_by_status`
  * Failure to serialize requests in `cloudflare_zero_trust_tunnel_cloudflared_config`
  * Undocumented field 'priority' on `zone_lockdown` resource
  * Missing importability for `cloudflare_zero_trust_device_default_profile_local_domain_fallback` and `cloudflare_account_subscription`
  * New resources:  
    * `cloudflare_schema_validation_operation_settings`
    * `cloudflare_schema_validation_schemas`
    * `cloudflare_schema_validation_settings`
    * `cloudflare_zero_trust_device_settings`
  * Other bug fixes  
For a more detailed look at all of the changes, see the [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.6.0) in GitHub.  
#### Issues Closed

  * [#5098: 500 Server Error on updating 'zero\_trust\_tunnel\_cloudflared\_virtual\_network' Terraform resource ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5098)
  * [#5148: cloudflare\_user\_agent\_blocking\_rule doesn’t actually support user agents ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5148)
  * [#5472: cloudflare\_zone showing changes in plan after following upgrade steps ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5472)
  * [#5508: cloudflare\_zero\_trust\_tunnel\_cloudflared\_config failed to serialize http request ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5508)
  * [#5509: cloudflare\_zone: Problematic Terraform behaviour with paused zones ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5509)
  * [#5520: Resource 'cloudflare\_magic\_wan\_static\_route' is not working ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5520)
  * [#5524: Optional fields cause crash in cloudflare\_zero\_trust\_tunnel\_cloudflared(s) when left null ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5524)
  * [#5526: Provider v5 migration issue: no import method for cloudflare\_zero\_trust\_device\_default\_profile\_local\_domain\_fallback ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5526)
  * [#5532: cloudflare\_zero\_trust\_access\_identity\_provider detects changes on every plan ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5532)
  * [#5561: cloudflare\_zero\_trust\_tunnel\_cloudflared: cannot rotate tunnel secret ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5561)
  * [#5569: cloudflare\_zero\_trust\_device\_custom\_profile\_local\_domain\_fallback not allowing multiple DNS Server entries ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5569)
  * [#5577: Panic modifying page\_rule resource ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5577)
  * [#5653: cloudflare\_zone\_setting resource schema confusion in 5.5.0: value vs enabled ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5653)  
If you have an unaddressed issue with the provider, we encourage you to check the [open issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.  
#### Upgrading  
If you are evaluating a move from v4 to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). 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 ↗](https://github.com/cloudflare/terraform-provider-cloudflare).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)

Jun 02, 2025
1. ### [Cloudflare User Groups & Enhanced Permission Policies are now in Beta](https://edgetunnel-b2h.pages.dev/changelog/post/2025-06-02-user-groups-beta/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)  
We're excited to announce the Public Beta launch of **User Groups for Cloudflare Dashboard** and **System for Cross Domain Identity Management (SCIM) User Groups**, expanding our RBAC capabilities to simplify user and group management at scale.  
We've also visually overhauled the **Permission Policies UI** to make defining permissions more intuitive.

**What's New**

**User Groups \[BETA\]**: [User Groups](https://edgetunnel-b2h.pages.dev/fundamentals/manage-members/user-groups/) are a new Cloudflare IAM primitive that enable administrators to create collections of account members that are treated equally from an access control perspective. User Groups can be assigned permission policies, with individual members in the group inheriting all permissions granted to the User Group. User Groups can be created manually or via our APIs.

**SCIM User Groups \[BETA\]**: Centralize & simplify your user and group management at scale by syncing memberships directly from your upstream identity provider (like Okta or Entra ID) to the Cloudflare Platform. This ensures Cloudflare stays in sync with your identity provider, letting you apply Permission Policies to those synced groups directly within the Cloudflare Dashboard.  
Note  
SCIM Virtual Groups (identified by the pattern `CF-<accountID>-<Role Name>` in your IdP) are deprecated as of 06/02/25\. We recommend migrating SCIM Virtual Groups implementations to use [SCIM User Groups](https://edgetunnel-b2h.pages.dev/fundamentals/account/account-security/scim-setup/). If you did not use Virtual Groups, no action is needed.

**Revamped Permission Policies UI \[BETA\]**: As Cloudflare's services have grown, so has the need for precise, role-based access control. We've given the Permission Policies builder a visual overhaul to make it much easier for administrators to find and define the exact permissions they want for specific principals.  
![Updated Permissions Policy UX](https://edgetunnel-b2h.pages.dev/_astro/2025-06-02-permissions-policy-ux.2wLEPgVX_7gPgJ.webp)  
Note  
When opting into the Beta for User Groups and Permission Policies, you'll be transitioning to a new experience. Please be aware that opting out isn't currently available.  
For more info:

  * [Get started with User Groups](https://edgetunnel-b2h.pages.dev/fundamentals/manage-members/user-groups/)
  * [Explore our SCIM integration guide](https://edgetunnel-b2h.pages.dev/fundamentals/account/account-security/scim-setup/)

May 19, 2025
1. ### [Terraform v5.5.0 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-05-19-terraform-v550-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.5.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases.  
#### Changes

  * Broad fixes across resources with recurring diffs, including, but not limited to:  
    * `cloudflare_zero_trust_gateway_policy`
    * `cloudflare_zero_trust_access_application`
    * `cloudflare_zero_trust_tunnel_cloudflared_route`
    * `cloudflare_zone_setting`
    * `cloudflare_ruleset`
    * `cloudflare_page_rule`
  * Zone settings can be re-applied without client errors
  * Page rules conversion errors are fixed
  * Failure to apply changes to `cloudflare_zero_trust_tunnel_cloudflared_route`
  * Other bug fixes  
For a more detailed look at all of the changes, see the [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.5.0) in GitHub.  
#### Issues Closed

  * [#5304: Importing cloudflare\_zero\_trust\_gateway\_policy invalid attribute filter value ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5304)
  * [#5303: cloudflare\_page\_rule import does not set values for all of the fields in terraform state ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5303)
  * [#5178: cloudflare\_page\_rule Page rule creation with redirect fails ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5178)
  * [#5336: cloudflare\_turnstile\_wwidget not able to update ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5336)
  * [#5418: cloudflare\_cloud\_connector\_rules: Provider returned invalid result object after apply ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5418)
  * [#5423: cloudflare\_zone\_setting: "Invalid value for zone setting always\_use\_https" ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5423)  
If you have an unaddressed issue with the provider, we encourage you to check the [open issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.  
#### Upgrading  
If you are evaluating a move from v4 to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). 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 ↗](https://github.com/cloudflare/terraform-provider-cloudflare).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)

May 06, 2025
1. ### [Terraform v5.4.0 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-05-06-terraform-v540-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.4.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases.  
#### Changes

  * Removes the `worker_platforms_script_secret` resource from the provider (see [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade#cloudflare%5Fworker%5Fsecret) for alternatives—applicable to both Workers and Workers for Platforms)
  * Removes duplicated fields in `cloudflare_cloud_connector_rules` resource
  * Fixes `cloudflare_workers_route` id issues [#5134 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5134) [#5501 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5501)
  * Fixes issue around refreshing resources that have unsupported response types Affected resources
    * `cloudflare_certificate_pack`
    * `cloudflare_registrar_domain`
    * `cloudflare_stream_download`
    * `cloudflare_stream_webhook`
    * `cloudflare_user`
    * `cloudflare_workers_kv`
    * `cloudflare_workers_script`
  * Fixes `cloudflare_workers_kv` state refresh issues
  * Fixes issues around configurability of nested properties without computed values for the following resources Affected resources
    * `cloudflare_account`
    * `cloudflare_account_dns_settings`
    * `cloudflare_account_token`
    * `cloudflare_api_token`
    * `cloudflare_cloud_connector_rules`
    * `cloudflare_custom_ssl`
    * `cloudflare_d1_database`
    * `cloudflare_dns_record`
    * `email_security_trusted_domains`
    * `cloudflare_hyperdrive_config`
    * `cloudflare_keyless_certificate`
    * `cloudflare_list_item`
    * `cloudflare_load_balancer`
    * `cloudflare_logpush_dataset_job`
    * `cloudflare_magic_network_monitoring_configuration`
    * `cloudflare_magic_transit_site`
    * `cloudflare_magic_transit_site_lan`
    * `cloudflare_magic_transit_site_wan`
    * `cloudflare_magic_wan_static_route`
    * `cloudflare_notification_policy`
    * `cloudflare_pages_project`
    * `cloudflare_queue`
    * `cloudflare_queue_consumer`
    * `cloudflare_r2_bucket_cors`
    * `cloudflare_r2_bucket_event_notification`
    * `cloudflare_r2_bucket_lifecycle`
    * `cloudflare_r2_bucket_lock`
    * `cloudflare_r2_bucket_sippy`
    * `cloudflare_ruleset`
    * `cloudflare_snippet_rules`
    * `cloudflare_snippets`
    * `cloudflare_spectrum_application`
    * `cloudflare_workers_deployment`
    * `cloudflare_zero_trust_access_application`
    * `cloudflare_zero_trust_access_group`
  * Fixed defaults that made `cloudflare_workers_script` fail when using Assets
  * Fixed Workers Logpush setting in `cloudflare_workers_script` mistakenly being readonly
  * Fixed `cloudflare_pages_project` broken when using "source"  
The detailed [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.4.0) is available on GitHub.  
#### Upgrading  
If you are evaluating a move from v4 to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). 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 either by reporting to our [GitHub repository ↗](https://github.com/cloudflare/terraform-provider-cloudflare), or by opening a [support ticket ↗](https://www.support.cloudflare.com/s/?language=en%5FUS).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare ↗](https://edgetunnel-b2h.pages.dev/terraform/)

Mar 26, 2025
1. ### [Updates to Account Home - Quick actions, traffic insights, Workers projects, and more](https://edgetunnel-b2h.pages.dev/changelog/post/2025-03-26-account-home-updates/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)  
![Updated Account Home](https://edgetunnel-b2h.pages.dev/_astro/2025-03-26-account-home-updates.CcOsD1dD_1WmntK.webp)  
Recently, Account Home has been updated to streamline your workflows:

  * **Recent Workers projects**: You'll now find your projects readily accessible from a new `Developer Platform` tab on Account Home. See recently-modified projects and explore what you can work our developer-focused products.
  * **Traffic and security insights**: Get a snapshot of domain performance at a glance with key metrics and trends.
  * **Quick actions**: You can now perform common actions for your account, domains, and even Workers in just 1-2 clicks from the 3-dot menu.
  * **Keep starred domains front and center**: Now, when you filter for starred domains on Account Home, we'll save your preference so you'll continue to only see starred domains by default.  
We can't wait for you to take the new Account Home for a spin.  
For more info:

  * [Try the updated Account Home ↗](https://dash.cloudflare.com/)
  * [Documentation on starred domains](https://edgetunnel-b2h.pages.dev/fundamentals/manage-domains/star-zones/)

Mar 21, 2025
1. ### [Dozens of Cloudflare Terraform Provider resources now have proper drift detection](https://edgetunnel-b2h.pages.dev/changelog/post/2025-03-21-resource-force-replacement-bug/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
In [Cloudflare Terraform Provider ↗](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, dozens of resources now have proper drift detection. Before this fix, these resources would indicate they needed to be updated or replaced — even if there was no real change. Now, you can rely on your `terraform plan` to only show what resources are expected to change.  
This issue affected [resources ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) related to these products and features:

  * API Shield
  * Argo Smart Routing
  * Argo Tiered Caching
  * Bot Management
  * BYOIP
  * D1
  * DNS
  * Email Routing
  * Hyperdrive
  * Observatory
  * Pages
  * R2
  * Rules
  * SSL/TLS
  * Waiting Room
  * Workers
  * Zero Trust

Mar 21, 2025
1. ### [Cloudflare Terraform Provider now properly redacts sensitive values](https://edgetunnel-b2h.pages.dev/changelog/post/2025-03-21-sensitive-values-redacted/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
In the [Cloudflare Terraform Provider ↗](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, sensitive properties of resources are redacted in logs. Sensitive properties in [Cloudflare's OpenAPI Schema ↗](https://raw.githubusercontent.com/cloudflare/api-schemas/refs/heads/main/openapi.yaml) are now annotated with `x-sensitive: true`. This results in proper auto-generation of the corresponding Terraform resources, and prevents sensitive values from being shown when you run Terraform commands.  
This issue affected [resources ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) related to these products and features:

  * Alerts and Audit Logs
  * Device API
  * DLP
  * DNS
  * Magic Visibility
  * Magic WAN
  * TLS Certs and Hostnames
  * Tunnels
  * Turnstile
  * Workers
  * Zaraz

Feb 03, 2025
1. ### [Terraform v5 Provider is now generally available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-03-terraform-v5-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
![Screenshot of Terraform defining a Zone](https://edgetunnel-b2h.pages.dev/_astro/2024-02-03-terraform-v5-screenshot.mW8OaFoS_Z2pw8Bq.webp)  
Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure.  
The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider ↗](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach.  
For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare ↗](https://edgetunnel-b2h.pages.dev/terraform/)

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/product-group/docs-collections/3/#page","headline":"Docs collections Changelog | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/product-group/docs-collections/3/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```