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

   Closes #66943
   
   Adds end-to-end coverage for the Go SDK executable coordinator path:
   
   - adds a go-sdk coordinator compose overlay with a Go builder and shared 
bundle volume
   - wires a new `go_sdk` airflow e2e test mode through Breeze, selective 
checks, and CI inputs
   - builds both Go fixture bundle shapes with `airflow-go-pack`
   - adds tests for a pure Go Dag and a Python `@task.stub(queue="go")` Dag 
routed to the executable coordinator
   
   Local verification:
   
   - `uv run ruff format ... && uv run ruff check ...`
   - `python -m py_compile ...`
   - `git diff --check`
   - `uv run yamllint airflow-e2e-tests/docker/go-sdk-coordinator.yml`
   - docker compose config validation for the base e2e compose plus go-sdk 
overlay
   - `docker run --rm -v 
"/home/ubuntu/.hermes/worktrees/airflow-66943-go/go-sdk:/go-sdk:ro" -v 
/tmp:/files -w /go-sdk golang:1.24-bookworm bash -c 'go run 
./cmd/airflow-go-pack ./example/bundle --output 
/files/go_sdk_pure_go_example_verify -- -ldflags "-X 
main.dagId=go_sdk_pure_go_example -X main.bundleName=go-sdk-pure-go" && go run 
./cmd/airflow-go-pack ./example/bundle --output 
/files/go_sdk_stub_example_verify -- -ldflags "-X 
main.dagId=go_sdk_stub_example -X main.bundleName=go-sdk-executable-bundles"'`
   - `docker run --rm -v 
"/home/ubuntu/.hermes/worktrees/airflow-66943-go/go-sdk:/go-sdk" -w /go-sdk 
golang:1.24-bookworm go test ./cmd/airflow-go-pack ./example/bundle`
   - `uv run python 
airflow-e2e-tests/tests/airflow_e2e_tests/go_sdk_tests/dags/stub_dag.py`
   - `uv run breeze testing airflow-e2e-tests --e2e-test-mode go_sdk --dry-run`
   
   Full `uv run breeze testing airflow-e2e-tests --e2e-test-mode go_sdk` could 
not run locally because the required prod image 
`ghcr.io/apache/airflow/main/prod/python3.10` was not present; Breeze prompted 
to build it and then failed in non-interactive stdin.


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