This article lists frequently asked questions about the Databricks extension for Visual Studio Code. See What is the Databricks extension for Visual Studio Code?.
Other languages, such as Scala or SQL
Delta Live Tables
Databricks SQL warehouses
Other IDEs, such as PyCharm
Full CI/CD integration
Databricks is aware of these requests and is prioritizing work to enable simple scenarios for local development and remote running of code. Please forward additional requests and scenarios to your Databricks account team. Databricks will incorporate your input into future planning.
How does the Databricks Terraform provider relate to the Databricks extension for Visual Studio Code?
Databricks continues to recommend the Databricks Terraform provider for managing your CI/CD pipelines in a predictable way. Please let your Databricks account team know how you might use an IDE to manage your deployments in the future. Databricks will incorporate your input into future planning.
The main features of dbx by Databricks Labs include:
Limited local development through the
CI/CD for Databricks jobs.
The Databricks extension for Visual Studio Code enables local development and remotely running Python code files on Databricks clusters, and remotely running Python code files and notebooks in Databricks jobs.
dbx can continue to be used for project scaffolding and CI/CD for Databricks jobs.
What happens if I already have an existing Databricks configuration profile that I created through the Databricks CLI?
You can select your existing configuration profile when you configure the Databricks extension for Visual Studio Code. With the extension and your code project opened, do the following:
In the Configuration pane, click the gear (Configure workspace) icon.
Enter your workspace instance URL, for example
In the Command Palette, select your existing configuration profile.
Yes. See the recommended solution in Error when synchronizing through a proxy.