Skip to content

Add sandbox filesystem commands and filer - #7372

Draft
akshaysingla-db wants to merge 8 commits into
mainfrom
akshaysingla-db/stack/sandbox-files-filer
Draft

akshaysingla-db wants to merge 8 commits into
mainfrom
akshaysingla-db/stack/sandbox-files-filer

Conversation

@akshaysingla-db

@akshaysingla-db akshaysingla-db commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

🥞 Stacked PR

Use this link to review incremental changes.


Changes

Add sandbox fs cp/ls/cat/mkdir/rm using a sandbox filer and the existing filesystem commands. Paths use SANDBOX:/absolute/path, with cached sandbox names supported. Copies skip existing files unless --overwrite is set.

Why

Sandbox file transfers need recursive copying and consistent filesystem commands. Uploads explicitly send overwrite=false by default and translate HTTP 412 into the filer's existing skip behavior. The pinned SDK predates this parameter, so upload uses its streaming HTTP client; other operations use generated methods. Requires server support for the overwrite parameter.

Tests

Added command and filer regression coverage for recursive downloads, overwrite/skip, metadata pagination, path encoding, and workspace routing. Formatting, diff checks, and focused Go lint pass. Functional tests have not been run.

This PR was written by Codex.

@akshaysingla-db
akshaysingla-db force-pushed the akshaysingla-db/stack/sandbox-files-filer branch from 4359bf9 to 47b4688 Compare November 5, 2026 05:46
@akshaysingla-db akshaysingla-db changed the title Add sandbox filesystem commands and filer [CJ-77441] Add sandbox filesystem commands and filer Nov 5, 2026
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: c69e06e

Run: 42254805257

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 273 24 3:59
✅​ aws-windows-latest-4core-16gb 275 22 3:48
✅​ azure linux-2core-8gb 272 24 4:07
✅​ azure-windows-latest-4core-16gb 274 22 3:25
✅​ gcp linux-2core-8gb 273 24 4:26
✅​ gcp-windows-latest-4core-16gb 275 22 3:47
Top 3 slowest tests (at least 2 minutes):
duration env testname
3:37 aws-windows-latest-4core-16gb TestAccept
3:16 azure-windows-latest-4core-16gb TestAccept
3:06 gcp-windows-latest-4core-16gb TestAccept

@pietern pietern changed the title [CJ-77441] Add sandbox filesystem commands and filer Add sandbox filesystem commands and filer Nov 6, 2026
pietern and others added 6 commits November 6, 2026 16:54
Models the server's semantics as observed on a live sandbox: uploads
always replace and create parents, deletes of absent paths succeed,
rename refuses an existing destination atomically, and most failures
share one generic error with only the status differing. Unknown upload
parameters such as overwrite are rejected, as on the real server.

Co-authored-by: Isaac <no-reply@databricks.com>
The server rejects the overwrite upload parameter, so every write failed.
Drop it and the hand-built HTTP client in favor of the typed SDK calls.
Exclusive writes now upload to a temporary file and rename it into place,
since rename refuses an existing destination atomically.

Map the server's generic errors to the Filer contract by statting the
path: reading a directory, listing a file, deleting a non-empty
directory, and creating a directory over a file. Report deletes of
absent paths and writes into missing parents as not found.

Test the filer against the testserver fake instead of per-test stubs,
which encoded server behavior that doesn't exist.

Co-authored-by: Isaac <no-reply@databricks.com>
Enabled by TEST_SANDBOX_ID. Also add a suite for concurrent exclusive
writes, run for the local and sandbox filers.

Co-authored-by: Isaac <no-reply@databricks.com>
One test per command (cp, ls, cat, mkdir, rm), run against the testserver
fake locally. With Cloud = true they also run against the existing
sandbox named by TEST_SANDBOX_ID, so a run doesn't create a sandbox;
cloud environments without one skip them.

Co-authored-by: Isaac <no-reply@databricks.com>
- Map rename errors other than "already exists" like upload errors.
- Give the exclusive-create temporary file a fixed-length name, so long
  target names stay within the filesystem's name limit, and stop claiming
  listings hide it.
- Keep cp's description of directory copies in the sandbox help, and
  explain why the fs command clears its help group.
- Share the sandbox cache key rule (profile, else host) in cacheProfile.
- Show the effect of cp --overwrite, and ignore the downloaded directory.
- Assert the full error for invalid sandbox paths.
- Drop the changelog fragment: the sandbox command is still hidden.

Co-authored-by: Isaac <no-reply@databricks.com>
- Report reading a symlink to a directory, and overwriting a directory,
  as "not a file" instead of the server's raw 409.
- Stop the fake's mkdirAll at "/" so it terminates after a recursive
  delete of the root.
- Show examples in each sandbox fs command's help, and say in cp's help
  that existing files are skipped without --overwrite.
- Mark which comments rely on the API docs rather than observed behavior.
- Capture --help as the first stanza of each sandbox fs acceptance test,
  and cover copying a file into an existing directory.

Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Commit: c69e06e43 | Workflow run

Regression test report

Selected 5 changed tests (limit=20, 0 not selected)

5 tests: regression=5 unreleased=0 coverage=0 failing=0
test branch main (dd0811b) latest (v1.24.0)
TestAccept/cmd/sandbox/fs/cat ✅ ❌ ❌
TestAccept/cmd/sandbox/fs/cp ✅ ❌ ❌
TestAccept/cmd/sandbox/fs/ls ✅ ❌ ❌
TestAccept/cmd/sandbox/fs/mkdir ✅ ❌ ❌
TestAccept/cmd/sandbox/fs/rm ✅ ❌ ❌
TestAccept/cmd/sandbox/fs/cat: branch ✅ | main (dd0811b) ❌ | latest (v1.24.0) ❌

main (dd0811b):

acceptance_test.go:1349: Diff:
        --- cmd/sandbox/fs/cat/output.txt
        +++ /tmp/TestAcceptcmdsandboxfscat65326740/002/output.txt
        @@ -1,16 +1,90 @@
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Help
         >>> [CLI] sandbox fs cat --help
        -Show file content. Use SANDBOX:/absolute/path for sandbox paths.
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
         Usage:
        -  databricks sandbox fs cat FILE_PATH [flags]
        +  databricks sandbox [command]
         
        -Examples:
        -  databricks sandbox fs cat my-sandbox:/tmp/file
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
         
         Flags:
        -  -h, --help   help for cat
        +  -h, --help   help for sandbox
         
         Global Flags:
               --debug            enable debug logging
        @@ -18,17 +84,150 @@
           -p, --profile string   ~/.databrickscfg profile
           -t, --target string    bundle target to use (if applicable)
         
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === cat a file
         >>> [CLI] sandbox fs cat [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/hello.txt
        -hello world!
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === cat a directory, then a missing path
         >>> [CLI] sandbox fs cat [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]
        -Error: not a file: /tmp/sandbox-fs-[UNIQUE_NAME]
        +Manage Databricks Sandbox environments.
         
        -Exit code: 1
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
         
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
... (55 more lines truncated, raise DATABRICKS_CLI_TEST_MAX_LOG to see more)

latest (v1.24.0): same output as main (dd0811b)

TestAccept/cmd/sandbox/fs/cp: branch ✅ | main (dd0811b) ❌ | latest (v1.24.0) ❌

main (dd0811b):

acceptance_test.go:1349: Diff:
        --- cmd/sandbox/fs/cp/output.txt
        +++ /tmp/TestAcceptcmdsandboxfscp704152206/002/output.txt
        @@ -1,31 +1,90 @@
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Help
         >>> [CLI] sandbox fs cp --help
        -Copy files and directories between your local filesystem and sandboxes.
        +Manage Databricks Sandbox environments.
         
        -  Use SANDBOX:/absolute/path for sandbox paths.
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
         
        -  Recursively copying a directory will copy all files inside directory
        -  at SOURCE_PATH to the directory at TARGET_PATH.
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
         
        -  When copying a file, if TARGET_PATH is a directory, the file will be created
        -  inside the directory, otherwise the file is created at TARGET_PATH.
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
         
        -  Files that already exist at the target are skipped unless --overwrite is set.
        -
         Usage:
        -  databricks sandbox fs cp SOURCE_PATH TARGET_PATH [flags]
        +  databricks sandbox [command]
         
        -Examples:
        -  databricks sandbox fs cp ./file my-sandbox:/tmp/file
        -  databricks sandbox fs cp --overwrite ./file my-sandbox:/tmp/file
        -  databricks sandbox fs cp -r my-sandbox:/tmp/dir ./local/dir
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
         
         Flags:
        -      --concurrency int   number of parallel copy operations (default 8)
        -  -h, --help              help for cp
        -      --overwrite         overwrite existing files
        -  -r, --recursive         recursively copy files from directory
        +  -h, --help   help for sandbox
         
         Global Flags:
               --debug            enable debug logging
        @@ -33,45 +81,183 @@
           -p, --profile string   ~/.databrickscfg profile
           -t, --target string    bundle target to use (if applicable)
         
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Upload a file
         >>> [CLI] sandbox fs cp local.txt [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        -local.txt -> [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         >>> [CLI] sandbox fs cat [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        -hello world!
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
... (121 more lines truncated, raise DATABRICKS_CLI_TEST_MAX_LOG to see more)

latest (v1.24.0):

acceptance_test.go:1349: Diff:
        --- cmd/sandbox/fs/cp/output.txt
        +++ /tmp/TestAcceptcmdsandboxfscp634992097/002/output.txt
        @@ -1,31 +1,90 @@
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Help
         >>> [CLI] sandbox fs cp --help
        -Copy files and directories between your local filesystem and sandboxes.
        +Manage Databricks Sandbox environments.
         
        -  Use SANDBOX:/absolute/path for sandbox paths.
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
         
        -  Recursively copying a directory will copy all files inside directory
        -  at SOURCE_PATH to the directory at TARGET_PATH.
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
         
        -  When copying a file, if TARGET_PATH is a directory, the file will be created
        -  inside the directory, otherwise the file is created at TARGET_PATH.
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
         
        -  Files that already exist at the target are skipped unless --overwrite is set.
        -
         Usage:
        -  databricks sandbox fs cp SOURCE_PATH TARGET_PATH [flags]
        +  databricks sandbox [command]
         
        -Examples:
        -  databricks sandbox fs cp ./file my-sandbox:/tmp/file
        -  databricks sandbox fs cp --overwrite ./file my-sandbox:/tmp/file
        -  databricks sandbox fs cp -r my-sandbox:/tmp/dir ./local/dir
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
         
         Flags:
        -      --concurrency int   number of parallel copy operations (default 8)
        -  -h, --help              help for cp
        -      --overwrite         overwrite existing files
        -  -r, --recursive         recursively copy files from directory
        +  -h, --help   help for sandbox
         
         Global Flags:
               --debug            enable debug logging
        @@ -33,45 +81,183 @@
           -p, --profile string   ~/.databrickscfg profile
           -t, --target string    bundle target to use (if applicable)
         
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Upload a file
         >>> [CLI] sandbox fs cp local.txt [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        -local.txt -> [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         >>> [CLI] sandbox fs cat [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]/file.txt
        -hello world!
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
... (123 more lines truncated, raise DATABRICKS_CLI_TEST_MAX_LOG to see more)
TestAccept/cmd/sandbox/fs/ls: branch ✅ | main (dd0811b) ❌ | latest (v1.24.0) ❌

main (dd0811b):

acceptance_test.go:1349: Diff:
        --- cmd/sandbox/fs/ls/output.txt
        +++ /tmp/TestAcceptcmdsandboxfsls1885346768/002/output.txt
        @@ -1,18 +1,90 @@
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Help
         >>> [CLI] sandbox fs ls --help
        -Lists files. Use SANDBOX:/absolute/path for sandbox paths.
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
         Usage:
        -  databricks sandbox fs ls DIR_PATH [flags]
        +  databricks sandbox [command]
         
        -Examples:
        -  databricks sandbox fs ls my-sandbox:/tmp
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
         
         Flags:
        -      --absolute   Displays absolute paths.
        -  -h, --help       help for ls
        -  -l, --long       Displays full information including size, file type and modification time since Epoch in milliseconds.
        +  -h, --help   help for sandbox
         
         Global Flags:
               --debug            enable debug logging
        @@ -20,22 +84,132 @@
           -p, --profile string   ~/.databrickscfg profile
           -t, --target string    bundle target to use (if applicable)
         
        +Use "databricks sandbox [command] --help" for more information about a command.
        +Manage Databricks Sandbox environments.
        +
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === List a directory
         >>> [CLI] sandbox fs ls [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]
        -dir
        -hello.txt
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
... (46 more lines truncated, raise DATABRICKS_CLI_TEST_MAX_LOG to see more)

latest (v1.24.0):

acceptance_test.go:1349: Diff:
        --- cmd/sandbox/fs/ls/output.txt
        +++ /tmp/TestAcceptcmdsandboxfsls2032538620/002/output.txt
        @@ -1,18 +1,90 @@
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === Help
         >>> [CLI] sandbox fs ls --help
        -Lists files. Use SANDBOX:/absolute/path for sandbox paths.
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
         Usage:
        -  databricks sandbox fs ls DIR_PATH [flags]
        +  databricks sandbox [command]
         
        -Examples:
        -  databricks sandbox fs ls my-sandbox:/tmp
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
         
         Flags:
        -      --absolute   Displays absolute paths.
        -  -h, --help       help for ls
        -  -l, --long       Displays full information including size, file type and modification time since Epoch in milliseconds.
        +  -h, --help   help for sandbox
         
         Global Flags:
               --debug            enable debug logging
        @@ -20,22 +84,132 @@
           -p, --profile string   ~/.databrickscfg profile
           -t, --target string    bundle target to use (if applicable)
         
        +Use "databricks sandbox [command] --help" for more information about a command.
        +Manage Databricks Sandbox environments.
        +
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
        +  -t, --target string    bundle target to use (if applicable)
        +
        +Use "databricks sandbox [command] --help" for more information about a command.
        +
         === List a directory
         >>> [CLI] sandbox fs ls [TEST_SANDBOX_ID]:/tmp/sandbox-fs-[UNIQUE_NAME]
        -dir
        -hello.txt
        +Manage Databricks Sandbox environments.
         
        +Sandbox provides SSH-accessible development environments backed by
        +microVM isolation. Each sandbox is a personal sandbox with pre-installed
        +tooling (Python, Node.js, Rust, Databricks CLI) and persistent storage.
        +
        +Getting started:
        +  databricks auth login --host https://...   # authenticate to a Databricks workspace
        +  databricks sandbox register                # generate and register an SSH key
        +  databricks sandbox create                  # provision a sandbox (becomes your default)
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +
        +Common workflows:
        +  databricks sandbox ssh                     # SSH to your default sandbox
        +  databricks sandbox ssh my-project          # SSH to a named sandbox
        +  databricks sandbox list                    # list your sandboxes
        +  databricks sandbox create                  # create a new sandbox
        +  databricks sandbox delete my-project       # delete a sandbox
        +  databricks sandbox status my-project       # show sandbox status
        +
        +Usage:
        +  databricks sandbox [command]
        +
        +Available Commands:
        +  config      Configure a Sandbox's name and auto-stop policy
        +  create      Create a new Sandbox environment
        +  default     Set the default Sandbox for SSH
        +  delete      Delete a Sandbox environment
        +  list        List your Sandbox environments
        +  register    Register this machine for sandbox SSH access
        +  ssh         SSH into a Sandbox environment
        +  ssh-key     Manage SSH keys registered with the sandbox service
        +  start       Start a stopped Sandbox environment
        +  status      Show Sandbox environment status
        +  stop        Stop a running Sandbox environment
        +
        +Flags:
        +  -h, --help   help for sandbox
        +
        +Global Flags:
        +      --debug            enable debug logging
        +  -o, --output type      output type: text or json (default text)
        +  -p, --profile string   ~/.databrickscfg profile
... (44 more lines truncated, raise DATABRICKS_CLI_TEST_MAX_LOG to see more)

2 more failure details omitted, see the full report in the run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants