jason810496 opened a new pull request, #67156:
URL: https://github.com/apache/airflow/pull/67156

   
   depends-on: refactor/go-sdk/dag-authoring-api (#67155 — must merge first; 
transitively on coordinator-runtime #67154)
   
   ## Why
   
   ADR 0004 settled on a self-contained executable as the Go bundle
   artefact: one binary that carries its own source and manifest in a
   footer, runs under both the go-plugin and the coordinator protocol,
   and exposes its bundle spec for introspection. This PR ships the
   tool that produces that artefact (`airflow-go-pack`) and the bundle
   server hooks it needs.
   
   ## What
   
   - `cmd/airflow-go-pack/pack.go` drives the build: it invokes the
     user's Go toolchain to compile their bundle main, then appends the
     source tree and manifest to the resulting binary via the new
     `internal/bundlefooter` package.
   - `cmd/airflow-go-pack/inspect.go` reads the footer back out — print
     the embedded manifest, optionally dump the source — so operators can
     verify what a binary contains without running it.
   - `cmd/airflow-go-pack/main.go` wires the subcommands and
     `--dump-bundle-spec` (the introspection contract from ADR 0001
     Option D); arg parsing treats everything after `--` as build flags
     to pass through to `go build`.
   - `bundle/bundlev1/bundlev1server/server.go` learns to detect a
     self-contained binary and serve its embedded source/manifest to the
     scanner instead of expecting a ZIP container.
   - `example/bundle/Justfile` is updated to build via `airflow-go-pack`,
     and `example/bundle/main.go` now reads its DAG id from an `-ldflags`
     variable so the test fixture can produce multiple bundles from one
     source tree.
   
   
   ---
   
   ##### 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]

Reply via email to