Publish otel-a2a-relay-core to an index; switch deploy Dockerfile from git-dep to wheel #31

Closed
opened 2026-06-02 06:18:52 +00:00 by coilysiren · 1 comment
Owner

Follow-up from splitting the deploy surface into otel-a2a-relay-deploy (#25).

The deploy repo's Dockerfile currently installs otel-a2a-relay-core as a pinned git dependency from this repo's core/ subdir (git+https://.../otel-a2a-relay.git@<ref>#subdirectory=core). That works but is the interim: it couples the image build back to this repo's git, needs git in the build stage, and is only reproducible if O2R_REF is pinned to a tag/commit.

The clean end-state is publishing otel-a2a-relay-core to an index:

  • Add a publish path here (uv build + publish on v* tags, or a release workflow) for otel-a2a-relay-core.
  • Then in otel-a2a-relay-deploy, switch the Dockerfile from the git dependency to a versioned wheel (uv pip install otel-a2a-relay-core==X.Y.Z) and drop the git stage.

This makes the dependency direction fully clean: the deploy repo consumes a published artifact instead of reaching into this repo's source tree.

Follow-up from splitting the deploy surface into `otel-a2a-relay-deploy` (#25). The deploy repo's Dockerfile currently installs `otel-a2a-relay-core` as a pinned git dependency from this repo's `core/` subdir (`git+https://.../otel-a2a-relay.git@<ref>#subdirectory=core`). That works but is the interim: it couples the image build back to this repo's git, needs `git` in the build stage, and is only reproducible if `O2R_REF` is pinned to a tag/commit. The clean end-state is publishing `otel-a2a-relay-core` to an index: - Add a publish path here (`uv build` + publish on `v*` tags, or a release workflow) for `otel-a2a-relay-core`. - Then in `otel-a2a-relay-deploy`, switch the Dockerfile from the git dependency to a versioned wheel (`uv pip install otel-a2a-relay-core==X.Y.Z`) and drop the git stage. This makes the dependency direction fully clean: the deploy repo consumes a published artifact instead of reaching into this repo's source tree.
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:23:50 +00:00
Commenting is not possible because the repository is archived.
No description provided.