Trigger recreate for immutable Lakebase database fields

acceptance/bundle/resources/database_catalogs/recreate/databricks.yml.tmpl

@@ -0,0 +1,14 @@
+bundle:
+  name: deploy-lakebase-catalog-recreate-$UNIQUE_NAME
+
+resources:
+  database_instances:
+    my_instance:
+      name: test-db-catalog-recreate-$UNIQUE_NAME
+      capacity: CU_1
+  database_catalogs:
+    my_catalog:
+      database_instance_name: ${resources.database_instances.my_instance.name}
+      database_name: DBNAME_PLACEHOLDER
+      name: my_catalog_$UNIQUE_NAME
+      create_database_if_not_exists: true

acceptance/bundle/resources/database_catalogs/recreate/out.requests.recreate.txt

@@ -0,0 +1,14 @@
+{
+  "method": "DELETE",
+  "path": "/api/2.0/database/catalogs/my_catalog_[UNIQUE_NAME]"
+}
+{
+  "body": {
+    "create_database_if_not_exists": true,
+    "database_instance_name": "test-db-catalog-recreate-[UNIQUE_NAME]",
+    "database_name": "my_database_v2",
+    "name": "my_catalog_[UNIQUE_NAME]"
+  },
+  "method": "POST",
+  "path": "/api/2.0/database/catalogs"
+}

acceptance/bundle/resources/database_catalogs/recreate/output.txt

@@ -0,0 +1,32 @@
+
+>>> [CLI] bundle deploy
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-catalog-recreate-[UNIQUE_NAME]/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Change an immutable catalog field: no update API, so the plan recreates it
+>>> [CLI] bundle plan
+recreate database_catalogs.my_catalog
+
+Plan: 1 to add, 0 to change, 1 to delete, 1 unchanged
+
+>>> [CLI] bundle deploy --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-catalog-recreate-[UNIQUE_NAME]/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+>>> [CLI] bundle destroy --auto-approve
+The following resources will be deleted:
+  delete resources.database_catalogs.my_catalog
+  delete resources.database_instances.my_instance
+
+This action will result in the deletion of the following Lakebase database instances.
+All data stored in them will be permanently lost:
+  delete resources.database_instances.my_instance
+
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-catalog-recreate-[UNIQUE_NAME]/default
+
+Deleting files...
+Destroy complete!

acceptance/bundle/resources/database_catalogs/recreate/script

@@ -0,0 +1,22 @@
+cleanup() {
+   trace $CLI bundle destroy --auto-approve
+   rm -f out.requests.txt
+}
+trap cleanup EXIT
+
+envsubst < databricks.yml.tmpl | sed "s/DBNAME_PLACEHOLDER/my_database/" > databricks.yml
+
+trace $CLI bundle deploy
+rm -f out.requests.txt
+
+title "Change an immutable catalog field: no update API, so the plan recreates it"
+sed "s/my_database/my_database_v2/" databricks.yml > databricks.yml.new
+mv databricks.yml.new databricks.yml
+
+trace $CLI bundle plan
+trace $CLI bundle deploy --auto-approve
+
+# The change must be a DELETE of the old catalog plus a POST creating the new
+# one. A PATCH would return 501 (the bug this guards against).
+jq --sort-keys 'select(.method != "GET" and (.path | contains("/database/catalogs")))' < out.requests.txt > out.requests.recreate.txt
+rm -f out.requests.txt

acceptance/bundle/resources/database_catalogs/recreate/test.toml

@@ -0,0 +1,10 @@
+# The Database API has no UpdateDatabaseCatalog endpoint (PATCH returns 501), so
+# any field change must go through delete + create. The direct engine handles
+# this; the terraform path would need an upstream provider fix and is excluded.
+EnvMatrix.DATABRICKS_BUNDLE_ENGINE = ["direct"]
+RecordRequests = true
+
+Ignore = [
+    "databricks.yml",
+    ".databricks",
+]

acceptance/bundle/resources/database_instances/recreate/databricks.yml.tmpl

@@ -0,0 +1,11 @@
+bundle:
+  name: deploy-lakebase-recreate-$UNIQUE_NAME
+
+sync:
+  paths: []
+
+resources:
+  database_instances:
+    my_database:
+      name: NAME_PLACEHOLDER
+      capacity: CU_1

acceptance/bundle/resources/database_instances/recreate/out.requests.rename.txt

@@ -0,0 +1,15 @@
+{
+  "method": "DELETE",
+  "path": "/api/2.0/database/instances/test-db-old-[UNIQUE_NAME]",
+  "q": {
+    "purge": "true"
+  }
+}
+{
+  "body": {
+    "capacity": "CU_1",
+    "name": "test-db-new-[UNIQUE_NAME]"
+  },
+  "method": "POST",
+  "path": "/api/2.0/database/instances"
+}

acceptance/bundle/resources/database_instances/recreate/output.txt

@@ -0,0 +1,35 @@
+
+>>> [CLI] bundle deploy
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-recreate-[UNIQUE_NAME]/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Rename the instance: name is immutable, so the plan recreates it
+>>> [CLI] bundle plan
+recreate database_instances.my_database
+
+Plan: 1 to add, 0 to change, 1 to delete, 0 unchanged
+
+>>> [CLI] bundle deploy --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-recreate-[UNIQUE_NAME]/default/files...
+
+This action will result in the deletion or recreation of the following Lakebase database instances.
+All data stored in them will be permanently lost:
+  recreate resources.database_instances.my_database
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+>>> [CLI] bundle destroy --auto-approve
+The following resources will be deleted:
+  delete resources.database_instances.my_database
+
+This action will result in the deletion of the following Lakebase database instances.
+All data stored in them will be permanently lost:
+  delete resources.database_instances.my_database
+
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-recreate-[UNIQUE_NAME]/default
+
+Deleting files...
+Destroy complete!

acceptance/bundle/resources/database_instances/recreate/script

@@ -0,0 +1,22 @@
+cleanup() {
+   trace $CLI bundle destroy --auto-approve
+   rm -f out.requests.txt
+}
+trap cleanup EXIT
+
+envsubst < databricks.yml.tmpl | sed "s/NAME_PLACEHOLDER/test-db-old-${UNIQUE_NAME}/" > databricks.yml
+
+trace $CLI bundle deploy
+rm -f out.requests.txt
+
+title "Rename the instance: name is immutable, so the plan recreates it"
+sed "s/test-db-old-${UNIQUE_NAME}/test-db-new-${UNIQUE_NAME}/" databricks.yml > databricks.yml.new
+mv databricks.yml.new databricks.yml
+
+trace $CLI bundle plan
+trace $CLI bundle deploy --auto-approve
+
+# The rename must be a DELETE of the old instance plus a POST creating the new
+# one. A PATCH to the renamed instance would 404 (the bug this guards against).
+jq --sort-keys 'select(.method != "GET" and (.path | contains("/database/instances")))' < out.requests.txt > out.requests.rename.txt
+rm -f out.requests.txt

acceptance/bundle/resources/database_instances/recreate/test.toml

@@ -0,0 +1,11 @@
+# A database instance name is immutable and the Database API has no rename
+# endpoint, so changing it must go through delete + create. Only the direct
+# engine handles this correctly; the terraform path needs an upstream provider
+# fix (marking name immutable in the spec) and is excluded here.
+EnvMatrix.DATABRICKS_BUNDLE_ENGINE = ["direct"]
+RecordRequests = true
+
+Ignore = [
+    "databricks.yml",
+    ".databricks",
+]

acceptance/bundle/resources/synced_database_tables/recreate/databricks.yml.tmpl

@@ -0,0 +1,24 @@
+bundle:
+  name: deploy-lakebase-synced-recreate-$UNIQUE_NAME
+
+resources:
+  database_instances:
+    my_instance:
+      name: test-db-synced-recreate-$UNIQUE_NAME
+      capacity: CU_1
+  database_catalogs:
+    my_catalog:
+      database_instance_name: ${resources.database_instances.my_instance.name}
+      database_name: my_database
+      name: my_catalog_$UNIQUE_NAME
+      create_database_if_not_exists: true
+  synced_database_tables:
+    my_synced_table:
+      name: ${resources.database_catalogs.my_catalog.name}.${resources.database_catalogs.my_catalog.database_name}.my_synced_table
+      database_instance_name: ${resources.database_instances.my_instance.name}
+      logical_database_name: ${resources.database_catalogs.my_catalog.database_name}
+      spec:
+        source_table_full_name: "main.test_schema.trips_source"
+        scheduling_policy: POLICY_PLACEHOLDER
+        primary_key_columns:
+          - id

acceptance/bundle/resources/synced_database_tables/recreate/out.requests.recreate.txt

@@ -0,0 +1,20 @@
+{
+  "method": "DELETE",
+  "path": "/api/2.0/database/synced_tables/my_catalog_[UNIQUE_NAME].my_database.my_synced_table"
+}
+{
+  "body": {
+    "database_instance_name": "test-db-synced-recreate-[UNIQUE_NAME]",
+    "logical_database_name": "my_database",
+    "name": "my_catalog_[UNIQUE_NAME].my_database.my_synced_table",
+    "spec": {
+      "primary_key_columns": [
+        "id"
+      ],
+      "scheduling_policy": "TRIGGERED",
+      "source_table_full_name": "main.test_schema.trips_source"
+    }
+  },
+  "method": "POST",
+  "path": "/api/2.0/database/synced_tables"
+}

acceptance/bundle/resources/synced_database_tables/recreate/output.txt

@@ -0,0 +1,41 @@
+
+>>> [CLI] bundle deploy
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-synced-recreate-[UNIQUE_NAME]/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Change an immutable synced-table field: no update API, so the plan recreates it
+>>> [CLI] bundle plan
+recreate synced_database_tables.my_synced_table
+
+Plan: 1 to add, 0 to change, 1 to delete, 2 unchanged
+
+>>> [CLI] bundle deploy --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-synced-recreate-[UNIQUE_NAME]/default/files...
+
+This action will result in the deletion or recreation of the following synced database tables.
+The synced data in the destination database will be lost (the source table is preserved):
+  recreate resources.synced_database_tables.my_synced_table
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+>>> [CLI] bundle destroy --auto-approve
+The following resources will be deleted:
+  delete resources.database_catalogs.my_catalog
+  delete resources.database_instances.my_instance
+  delete resources.synced_database_tables.my_synced_table
+
+This action will result in the deletion of the following Lakebase database instances.
+All data stored in them will be permanently lost:
+  delete resources.database_instances.my_instance
+
+This action will result in the deletion of the following synced database tables.
+The synced data in the destination database will be lost (the source table is preserved):
+  delete resources.synced_database_tables.my_synced_table
+
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/deploy-lakebase-synced-recreate-[UNIQUE_NAME]/default
+
+Deleting files...
+Destroy complete!

acceptance/bundle/resources/synced_database_tables/recreate/script

@@ -0,0 +1,22 @@
+cleanup() {
+   trace $CLI bundle destroy --auto-approve
+   rm -f out.requests.txt
+}
+trap cleanup EXIT
+
+envsubst < databricks.yml.tmpl | sed "s/POLICY_PLACEHOLDER/SNAPSHOT/" > databricks.yml
+
+trace $CLI bundle deploy
+rm -f out.requests.txt
+
+title "Change an immutable synced-table field: no update API, so the plan recreates it"
+sed "s/scheduling_policy: SNAPSHOT/scheduling_policy: TRIGGERED/" databricks.yml > databricks.yml.new
+mv databricks.yml.new databricks.yml
+
+trace $CLI bundle plan
+trace $CLI bundle deploy --auto-approve
+
+# The change must be a DELETE of the old synced table plus a POST creating the
+# new one. A PATCH would return 501 (the bug this guards against).
+jq --sort-keys 'select(.method != "GET" and (.path | contains("/database/synced_tables")))' < out.requests.txt > out.requests.recreate.txt
+rm -f out.requests.txt

acceptance/bundle/resources/synced_database_tables/recreate/test.toml

@@ -0,0 +1,10 @@
+# The Database API has no UpdateSyncedDatabaseTable endpoint (PATCH returns 501),
+# so any field change must go through delete + create. The direct engine handles
+# this; the terraform path would need an upstream provider fix and is excluded.
+EnvMatrix.DATABRICKS_BUNDLE_ENGINE = ["direct"]
+RecordRequests = true
+
+Ignore = [
+    "databricks.yml",
+    ".databricks",
+]