jason810496 opened a new pull request, #67155:
URL: https://github.com/apache/airflow/pull/67155
depends-on: refactor/go-sdk/coordinator-runtime (#67154 — must merge first)
## Why
The Go authoring API today exposes `AddDag(name)` and `AddTask(fn)`
with no way to set the things a real DAG needs — schedule, tags,
queue, retries, or downstream relationships — so any non-trivial Go
DAG has to reach around the registry. This PR adds the missing
configuration surface and the downstream argument so users can author
multi-task DAGs in pure Go without escape hatches.
## What
- `bundlev1/registry.go`: `AddDag` now takes an optional `DagSpec`
(schedule, description, tags, etc.) and `AddTask` now takes an
optional `TaskSpec` (queue, retries, …) plus a downstream task-id
list. The registry materialises both into the serialised DAG so the
coordinator sees the same shape Python sees.
- `pkg/execution/serde.go` learns to encode the new spec fields and
downstream edges into Airflow's task/DAG payload.
- Example bundle (`example/bundle/main.go`) updates to the new
signatures so it doubles as a worked example of the API.
- Tests: `registry_test.go`, `serde_test.go`, `integration_test.go`,
and `worker/runner_test.go` cover the new spec/downstream paths.
---
##### Was generative AI tooling used to co-author this PR?
- [x] Yes, with help of Claude Code Opus 4.7 following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
