Pieter Noordhuis

Have you tried `databricks sync` before? It observes the ignore rules from `.gitignore`. The command is a one-way sync only; from your client into the Databricks workspace.

Sort of related -- you can specify the `BUNDLE_ROOT` environment variable to point the CLI at the bundle root if it cannot be derived from your working directory. It still...

Thanks for raising this and additional context. I'm contemplating the implications of doing this w.r.t. relative paths for both the bundle root as well as the includes. Today, we anchor...

> I'm trying to understand what is the benefit of anchoring paths to the bundle root? Doing this means you have to put the bundle at the repo root anyways,...

@ericfeunekes It is, though the specifics are tbd. In the comments above we were talking about the bundle root and the path where `databricks.yml` is specified. One consideration we didn't...

Update: we have implemented this (albeit slightly differently) in #1694. To include directories outside the bundle root directory, you can add a `paths` section to the `sync` block like so:...

This has been released as part of v0.227.0.

Thanks for reporting. We're aware this is not possible today. The underlying issue is that notebooks specifically cannot be read through the FUSE mount of the workspace filesystem and we...

Thanks for the ping on this thread! We're currently working on fixing this. You can find relevant work (in case you're interested) in https://github.com/databricks/cli/pull/1452 and https://github.com/databricks/cli/pull/1457. In those PRs we're...

I didn't update this issue when the functionality landed. It is possible to run bundle deployment from DBR as of v0.223.0. If the bundle is located in `/Workspace` then instead...