// AI Platform Drift

Cloudflare Terraform provider v5.29.0 changes AI Search import IDs and data source arguments

Cloudflare developer changelog · published 2026-11-15 06:34 UTC
ACTION NEEDED MIGRATE API
WHAT CHANGEDCloudflare Terraform provider v5.29.0 changes the cloudflare_ai_search_instance import ID format from <account_id>/<id> to <account_id>/<namespace>/<id>. The cloudflare_ai_search_instance and cloudflare_ai_search_instances data sources now require a namespace argument. The filter.namespace argument is removed from cloudflare_ai_search_instances. The cloudflare_ai_search_instance resource adds an optional namespace argument that defaults to "default".
WHY IT MATTERSExisting Terraform configurations that import AI Search instances or use AI Search data sources will fail after upgrading to v5.29.0 unless the import commands and data source blocks are updated to include the namespace parameter.
WHAT TO DOBefore upgrading to Terraform provider v5.29.0, update import commands to the format terraform import cloudflare_ai_search_instance.name <account_id>/default/<id> for default namespace instances. Add namespace = "default" to all cloudflare_ai_search_instance and cloudflare_ai_search_instances data source blocks. Remove any filter.namespace arguments from cloudflare_ai_search_instances data sources.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## AI Search - Manage AI Search instances in any namespace with Terraform
+https://developers.cloudflare.com/changelog/post/2026-11-13-terraform-namespaces/
+Fri, 13 Nov 2026 00:00:00 GMT
+
+Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace, not only default.
+The cloudflare_ai_search_instance resource has a new namespace argument. It defaults to default, so existing configurations keep managing the same instances.
+resource "cloudflare_ai_search_namespace" "support" {
+account_id = var.account_id
+name = "support"
+}
+
+resource "cloudflare_ai_search_instance" "docs" {
+account_id = var.account_id
+id = "docs"
+namespace = cloudflare_ai_search_namespace.support.name
+}
+You can import existing instances and namespaces:
+terraform import cloudflare_ai_search_instance.docs <account_id>/support/docs
+terraform import cloudflare_ai_search_namespace.support <account_id>/support
+The data sources read instances from the namespace you set:
+data "cloudflare_ai_search_instance" "docs" {
+account_id = var.account_id
+namespace = "support"
+id = "docs"
+}
+
+data "cloudflare_ai_search_instances" "support" {
+account_id = var.account_id
+namespace = "support"
+}
+When you upgrade to v5.29.0, review these changes:
+
+The cloudflare_ai_search_instance import ID now includes the namespace: <account_id>/<namespace>/<id>. For instances in the default namespace, use <account_id>/default/<id>.
+The cloudflare_ai_search_instance and cloudflare_ai_search_instances data sources require namespace. Set namespace = "default" for instances in the default namespace.
+cloudflare_ai_search_instances returns the instances in one namespace. The filter.namespace argument of cloudflare_ai_search_instance is removed.
+Changing namespace replaces the instance.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningBreaking changes to Terraform provider API require configuration updates and migration steps.
signalsbreaking API change: import ID format changed · breaking API change: data sources now require namespace argument · breaking API change: filter.namespace argument removed · breaking API change: namespace argument added to resource · new provider version v5.29.0 with incompatible changes · migration required for existing Terraform configurations
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)