jason810496 opened a new issue, #66939:
URL: https://github.com/apache/airflow/issues/66939

   ### Background
   
   Today the Go SDK has a developer-grade README
   (`go-sdk/README.md`) covering the Edge Worker quickstart and four ADRs
   covering the bundle format. There is no Airflow-docs-site material for:
   
   - Authoring a pure-Go Dag with the executable coordinator (the
     non-Edge-Worker path introduced by ADR 0003).
   - Authoring a Python `@task.stub` Dag that delegates to a Go bundle.
   - Administrator-side multi-lang setup: configuring
     `[executable] bundles_folder`, queue routing via `[sdk] queue_to_sdk`,
     bundle-deployment layout.
   
   The Java-SDK side has the same gap and is tracking it under #66326.
   
   ### What needs to happen
   
   1. Authoring guide: pure-Go Dag, including the `bundlev1server.Serve`
      entrypoint and how `airflow-go-pack` packages it.
   2. Authoring guide: Python `@task.stub(queue="go")` Dag that delegates
      to a Go bundle.
   3. Admin guide: multi-lang setup (config keys, queue->runtime mapping,
      `bundles_folder` layout).
   4. Bundle-spec docs cross-link from the Go SDK README to
      `providers/sdk/executable/docs/bundle-spec.rst`.
   
   ### Acceptance criteria
   
   - All four sections land under `providers/sdk/executable/docs/` (or the
     Airflow docs site) and are linked from the Go-SDK landing material.
   - Examples are runnable end-to-end via Breeze.
   
   ### Context
   
   - Java parallel: #66326 (Add User-facing Docs for Multi-lang).
   - Existing material: `go-sdk/README.md`, 
`go-sdk/adr/0003-coordinator-protocol-msgpack-ipc.md`,
     `go-sdk/adr/0004-self-contained-executable-bundle.md`,
     `providers/sdk/executable/docs/bundle-spec.rst`.
   
   ---
   Drafted-by: Claude Code (Opus 4.7) (no human review before posting)


-- 
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