Integrate DAG editor in Airflow
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- git, kubernetes
调研方向
首先检查 operator 的 CRD 配置，以及 issue 中提到的现有 GitSync 和 Open Policy Agent 集成。评估 Airflow 代码编辑器如何适配 Docker 镜像、GitSync 和基于 PVC 的 DAG 存储。完成的标准是：有一个配置好的编辑器，具备基于角色的访问控制，并且为通过 UI 编写的 DAG 定义了配置和持久化路径。
由索引模型根据 Issue 内容生成。
描述
Current Situation
We offer the customer to inject DAGs into airflow in two ways:
- Customers can mount a
configMapinto the Airflow pod and store theDAGsthere. - Customers can use GitSync to host
DAGsin an git repository.
Both ways need a way to interact either with kubernetes itself or with git.
Proposed Situation
Customers can log into Airflow and edit DAGs in the Airflow UI.
To archive this, we'd need to include an editor in airflow dockerimage and make it configurable through the operators CRD. I'd propose https://github.com/andreax79/airflow-code-editor as an candidate.
Advantage
Now where https://github.com/stackabletech/airflow-operator/pull/573 is merged, we offer deeply integrated Open Policy Agent support, which would lead to the advantage to offer role based editor access to data engineers or product owners. There wouldn't be a need to have knowledge of kuberentes or git to modify, develop and deploy DAGs. In my opinion this would increase usability and accessibility of Airflow and could empower the customer.
Additionally, it would make the development process of DAGs much easier as we would move from develop -> deploy -> test to develop -> test.
Evaluation
I expect this to be a rather large feature. We'd need to think about roles and how to configure those for editor access without OPA too. We need to be able to integrate with GitSync and implement access, provisioning and usage of PVCs to store DAGs written in the Airflow UI. Role based access may also apply to files stored in PVCs. We introduce at least another dependency we might need to maintain.
- 主要语言
- Rust
- 星标
- 32
- 派生
- 6
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 15
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stackabletech/airflow-operator 的其他 Issue
-
type/bug
难度 2/5 1-3 小时 新手友好度 72/100
stackabletech/airflow-operator#855 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue type/feature-improvement
难度 4/5 3-5 天 新手友好度 45/100
stackabletech/airflow-operator#760 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 42/100
stackabletech/airflow-operator#697 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
stackabletech/airflow-operator#638 ·
维护者通常 1 天内回复
-
type/feature-new
难度 5/5 一周以上 新手友好度 25/100
stackabletech/airflow-operator#592 · 1 条评论 ·
维护者通常 1 天内回复
查看 stackabletech/airflow-operator 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 5 天内回复
-
state:triage-needed
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
ktuner keeps a stale ledger path and can never restore that entry可能已有人在做 @Frun1na 今天认领。 未关闭component:ktuner
难度 2/5 1-3 小时 新手友好度 75/100
agentic-os-org/ANOLISA#6483 · 1 条评论 ·
维护者通常 1 天内回复
-
resource-submission validation-passed
难度 1/5 1 小时以内 新手友好度 85/100
hesreallyhim/awesome-claude-code#3095 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复