Support for data sources

未关闭
  • 哪里不对？
#3,460 2 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
go, terraform
领域
cli, devops

调研方向

首先跟踪 DAB 资源定义的处理方式，并将提议的 bind 语法与 Terraform 数据源的行为进行比较。确定预期使用的是 bind 还是单独的 sources 概念，然后定义所有权和比较规则，并使用 bronze 资源等 schema 示例进行验证。

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

描述

DABs Enhancement No Autoclose

In Terraform, you can declare a data source which is essentially a resource that is externally managed, but must exist.

The Databricks Terraform provider already supports this for a number of resources including schemas, e.g.

data "databricks_schemas" "sandbox" {
  catalog_name = "sandbox"
}

DABs should use this to support defining resources such as schemas that are required to exist in the catalog, but which aren't managed by the bundle.

The motivation is that sometimes we want to reference resources without having the bundle own them (for example schemas).

Syntax

We could introduce a property bind which would default to true.

This is how it would look for a schema resource:

resources:
  schemas:
    bronze:
      bind: false
      name: bronze
      catalog_name: dev

Setting bind: false would mean that the resource should already exist and we'll compare the resource data to the definition.

An alternative would be to introduce a concept of sources which would be in addition to resources. This would allow these sources to be specified by name without a complete definition, similar to Terraform's data sources:

sources:
  schemas:
    bronze:
      name: bronze
      catalog_name: dev
主要语言
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 摘要。