[Feature Request] Clean up local bundle cache (.databricks folder) when identity or root path is changed

未关闭
#2,431 5 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@andrewnester 已经在做这个了。

开始于 2025年12月8日。

评估

这个 Issue 还没有评估数据。

描述

DABs Enhancement No Autoclose
Describe the issue

I have inhertited a project were bundles are dynamically build in the same folder.

/
/use case a
/use case b
/databricks.yaml.template (includes workflows from a and b dynamically)

during CI/CD
/databicks.yaml (with use case a, job a) is build and deployed
.. later
/databicks.yaml (with use case b, with job b) is build and deployed

I have the feeling that this is too complex and can also be achieved in a static fashion.
I think this also explains why we only see bundle b deployed and not a.

But this non the less raises the question which attributes are used to make the identity of a bundle or more specifically its ressources.

What combination of attributes (source path, target path, bundle name, ...) is used to decide which resources are needed to be deleted, adjusted or created.
Can you please shed some light on it independent of my problem above?

Configuration

See above

Steps to reproduce the behavior
  1. A set of bundles (a, b, c) is dynamically created
  2. After deployment of bundle a, b, c only the workflow c exists, a and b are not there.
Expected Behavior

None so far, only a question. I also haven't found a quick answer in the documentation.

Actual Behavior

Only the last deployed bundle exists. A and b seem to get created and then deleted again - I believe since the mechanisms used identified all three bundles as beeing the same.

OS and CLI version

Databricks CLI v0.238.0

Is this a regression?

No

Debug Logs

could be provided upon request, but will have to be cleaned up

主要语言
Go
星标
427
派生
267
平均合并
2 天 1 小时
30 天内合并 PR
233

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

databricks/cli 的其他 Issue

查看 databricks/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。