bundle: Add genie_space resource (direct engine only) (#5282)

## Summary

Introduces a new `genie_space` bundle resource (direct-engine only) that
mirrors the existing `dashboard` pattern.

Resolves #3008 
Closes #4191 

## Test plan
- [x] CI
- [x] Cloud tests pass
- [x] Manual live workspace verification

This pull request and its description were written by Isaac.

Author: janniklasrose

NEXT_CHANGELOG.md

@@ -18,6 +18,7 @@
 * Set the default `data_security_mode` to `DATA_SECURITY_MODE_AUTO` in bundle templates ([#5452](https://github.com/databricks/cli/pull/5452)).
 * Mark vector search index index_subtype as backend_default to prevent drift after deployment ([#5454](https://github.com/databricks/cli/pull/5454)).
 * `bundle deployment migrate`: handle resources added to or removed from `databricks.yml` since the last Terraform deploy ([#5463](https://github.com/databricks/cli/pull/5463)).
+* Add the `genie_spaces` bundle resource for managing Databricks Genie spaces as code, plus `bundle generate genie-space` to import an existing space. Direct deployment engine only ([#5282](https://github.com/databricks/cli/pull/5282)).
 
 ### Dependency updates
 

acceptance/.gitattributes

@@ -4,6 +4,7 @@
 # uploading the file's content to a workspace.
 *.txt text eol=lf
 *.lvdash.json text eol=lf
+*.geniespace.json text eol=lf
 
 # The out.test.toml file is autogenerated based on the merged test.toml view.
 out.test.toml linguist-generated=true

acceptance/bundle/deployment/bind/genie_space/databricks.yml.tmpl

@@ -0,0 +1,13 @@
+bundle:
+  name: test-bundle-$UNIQUE_NAME
+
+resources:
+  genie_spaces:
+    genie_space1:
+      title: $GENIE_SPACE_TITLE
+      warehouse_id: "test-warehouse-id"
+      parent_path: /Users/$CURRENT_USER_NAME
+      # Inline body matches the out-of-band-created space byte-for-byte, so the
+      # only possible post-bind drift signal is the etag.
+      serialized_space:
+        version: 1

acceptance/bundle/deployment/bind/genie_space/out.test.toml

@@ -0,0 +1,37 @@
+
+>>> [CLI] bundle deployment bind genie_space1 [GENIE_SPACE_ID] --auto-approve
+Updating deployment state...
+Successfully bound genie_space with an id '[GENIE_SPACE_ID]'
+Run 'bundle deploy' to deploy changes to your workspace
+
+>>> [CLI] bundle plan
+Plan: 0 to add, 0 to change, 0 to delete, 1 unchanged
+
+>>> [CLI] bundle deploy
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle-[UNIQUE_NAME]/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+>>> [CLI] genie get-space [GENIE_SPACE_ID]
+{
+  "parent_path": "/Users/[USERNAME]",
+  "title": "test genie space [UNIQUE_NAME]",
+  "warehouse_id": "test-warehouse-id"
+}
+
+>>> [CLI] bundle deployment unbind genie_space1
+Updating deployment state...
+
+>>> [CLI] bundle destroy --auto-approve
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/test-bundle-[UNIQUE_NAME]/default
+
+Deleting files...
+Destroy complete!
+
+>>> [CLI] genie get-space [GENIE_SPACE_ID]
+{
+  "parent_path": "/Users/[USERNAME]",
+  "title": "test genie space [UNIQUE_NAME]",
+  "warehouse_id": "test-warehouse-id"
+}

acceptance/bundle/deployment/bind/genie_space/output.txt

@@ -0,0 +1,30 @@
+GENIE_SPACE_TITLE="test genie space $UNIQUE_NAME"
+
+export GENIE_SPACE_TITLE
+envsubst < databricks.yml.tmpl > databricks.yml
+
+# Create a Genie space out of band, then bind the bundle resource to it.
+GENIE_SPACE_ID=$($CLI genie create-space "test-warehouse-id" '{"version":1}' --title "${GENIE_SPACE_TITLE}" | jq -r '.space_id')
+
+cleanupRemoveGenieSpace() {
+    $CLI genie trash-space "${GENIE_SPACE_ID}"
+}
+trap cleanupRemoveGenieSpace EXIT
+
+trace $CLI bundle deployment bind genie_space1 "${GENIE_SPACE_ID}" --auto-approve
+
+# Bind must copy the remote etag into state, so the first plan after bind is
+# clean. Without that, the etag drift signal (empty stored vs remote) would
+# produce a bogus update here.
+trace $CLI bundle plan
+
+trace $CLI bundle deploy
+
+trace $CLI genie get-space "${GENIE_SPACE_ID}" | jq --sort-keys '{title, parent_path, warehouse_id}'
+
+trace $CLI bundle deployment unbind genie_space1
+
+trace $CLI bundle destroy --auto-approve
+
+# Read the Genie space again (expecting it still exists and is not deleted):
+trace $CLI genie get-space "${GENIE_SPACE_ID}" | jq --sort-keys '{title, parent_path, warehouse_id}'

acceptance/bundle/deployment/bind/genie_space/script

@@ -0,0 +1,13 @@
+Local = true
+
+# Genie spaces are only deployed via the direct deployment engine.
+EnvMatrix.DATABRICKS_BUNDLE_ENGINE = ["direct"]
+
+# Uses a literal warehouse id and a version-sensitive serialized_space, so this
+# lifecycle test runs against the local mock server only (overrides the Cloud=true
+# inherited from acceptance/bundle/deployment/test.toml).
+Cloud = false
+
+[[Repls]]
+Old = "[0-9a-f]{32}"
+New = "[GENIE_SPACE_ID]"

acceptance/bundle/deployment/bind/genie_space/test.toml

@@ -0,0 +1,2 @@
+bundle:
+  name: genie-space-generate

acceptance/bundle/generate/genie_space/databricks.yml

@@ -0,0 +1,7 @@
+{
+    "title": "test genie space",
+    "description": "test description",
+    "parent_path": "/Workspace/test-$UNIQUE_NAME",
+    "warehouse_id": "test-warehouse-id",
+    "serialized_space": "{\"tables\":[],\"questions\":[]}"
+}