VS Code Extension Sync Destination Changed Unexpectedly

nirquant — Wed, 12 Feb 2025 15:13:50 GMT

I recently updated my Databricks VS Code extension from version 1.4.0 to 2.4.0. After the update, I noticed that:

The "Configure Sync Destination" button is missing.
The sync destination format has changed to a remote folder instead of the previous setup.
The default sync destination is now (path/files), whereas my jobs and clusters were originally configured to (path).

This change is causing issues with my workflow. How can I either:

Restore the original sync destination to (path)?
Reconfigure the sync destination manually in the new extension version?

Any guidance or workarounds would be appreciated!

Re: VS Code Extension Sync Destination Changed Unexpectedly

mark_ott — Tue, 04 Nov 2025 17:48:55 GMT

The upgrade to Databricks VS Code extension v2.4.0 changed the sync destination system from the previous workspace directory setup, removing the "Configure Sync Destination" button and setting the default to a more rigid remote folder structure (commonly with a /files subdirectory). This change impacts workflows that depend on the older directory path.

Restoring the Original Sync Destination

The extension now expects sync destinations to follow the new model, and reverting directly to the old "path" format is not natively supported in v2.4.0.
However, you can manually adjust the workspace path in your project's .databricks/project.json file. Set "workspacePath" to your desired directory, such as "/Workspace/path" instead of "/Workspace/path/files". Make sure this matches the target you want to sync to in Databricks.
After editing this config, restart VS Code and refresh the Databricks extension. Note that a mismatch between workspace and local names produces warnings, which can usually be ignored unless strict name matching is required for your workflow.

Manually Reconfiguring Sync Destination

Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
Type and select “Databricks: Create New Sync Destination” or similar options (label may vary slightly).
Choose or create the destination path. To reuse a previous path, select from existing directories shown in the Command Palette.
If you want to work around the new default, manually edit the .databricks/project.json file as explained above.
Start synchronization by clicking the sync icon in the configuration pane.

Workarounds and Tips

Changes are now one-way: files synced to Databricks do not sync back to your local repo. Only do edits locally and sync them up.
Custom workspace configuration beyond the UI may require manual JSON edits as described, and persistent issues with path configuration can sometimes be resolved by uninstalling and reinstalling the extension.
For advanced configuration or troubleshooting, check logs using “Databricks: Open full logs” from the Command Palette, and verify all paths in your .databricks/project.json are correct.

Summary Table

Workflow Issue	Solution
"Configure Sync Destination" missing	Use Command Palette and manually edit `.databricks/project.json`
New remote folder sync format	Change `"workspacePath"` in your config file back to original value
Default sync destination subfolder	Remove or rename `/files` in path config and re-sync