Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bundle reports schema update for every deployment

未关闭
#6,986 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
cli, data

调研方向

The bug sits in how the bundle deployment state compares a bound schema against the remote Unity Catalog schema, so start with the schema resource handling in the bundle deploy code and the deployment-state diff. Reproduce by binding an existing schema and running deploy twice; the expected result is no 'Updated schemas' line on the second run. Done means the second deploy reports no changes and the owner-null diff no longer appears.

由索引模型根据 Issue 内容生成。

描述

DABs
Describe the issue

When deploying bundle, schemas that existed before and were bound to the bundle are reported as updated when there are no changes made to the resource.

Configuration
resources:
  schemas:
    test_schema:
      name: test_schema
      catalog_name: test_catalog
Steps to reproduce the behavior
  1. Create schema to catalog with SQL CREATE SCHEMA test_catalog.test_schema.
  2. Run databricks bundle deployment bind test_schema test_catalog.test_schema.
  3. Bind command reports that changes were detected:
    Changes detected:
       ~ properties: {"owner":"root"} -> null
    
    Approve the detected changes.
  4. Run databricks bundle deploy.
  5. Run databricks bundle deploy again.
Expected Behavior

The first deployment should apply the detected changes in the deployment and second deployment should not report schema as updated.

Actual Behavior

The first as well as the second bundle deployment reports that the test_schema was updated: Updated schemas.test_schema.

OS and CLI version

Windows 11, 1.20.0

Is this a regression?

Haven't tested with other versions.

主要语言
Go
星标
404
派生
246
平均合并
1 天 14 小时
30 天内合并 PR
281

环境准备

  • 提供 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 摘要。