Skip to content

feat(docker): source connectors from the runtime catalog - #152

Merged
tnunamak merged 1 commit into
integration/unified-stackfrom
feat/docker-connectors-from-catalog
Sep 16, 2026
Merged

tnunamak merged 1 commit into
integration/unified-stackfrom
feat/docker-connectors-from-catalog

Conversation

@tnunamak

Copy link
Copy Markdown
Contributor

deploy/docker/Dockerfile:32-60 made every production image copy pdpp-polyfill-connectors-0.0.1.tgz, and :117-132 derived Patchright from that tarball; this coupled first boot to the devendored package instead of letting the active catalog/install roots supply executable connectors. The RI also imported polyfill helpers directly across runtime paths, so removing the tarball would fail startup rather than produce an empty, catalog-backed no-install state.

This patch keeps the reference-contract tarball, removes the connector tarball from the production context and --omit=dev install, declares the transitive runtime packages directly, and pins browser setup to RI's direct Patchright dependency. server/polyfill-connectors-runtime.ts provides the optional host/conformance boundary with empty and fail-closed production fallbacks. PDPP_CONNECTOR_PRELOAD_DIR selects the file-backed install roots for air-gapped connector activation.

Evidence:

  • The Docker build passed, and the container started both listeners without @pdpp/polyfill-connectors or its tarball.
  • Discovery and OAuth metadata returned 200; unauthenticated owner catalog/status returned the expected 401 route guard; Patchright reported 1.63.0.
  • Focused RI tests passed 19/19, composed-origin passed 2/2, and console pure tests passed 19/19.
  • Workspace and console builds passed.

Not verified: a live authenticated GHCR catalog read; the owner catalog path is covered by the fixture test and container auth boundary. Existing RI typecheck and repo-wide check noise remains documented in the report.

Assisted-by: AI

Keep production Docker images independent of the devendored polyfill connector
package while preserving host conformance coverage. Declare its transitive runtime
dependencies directly and route optional helpers through a fail-closed boundary so
catalog installs and preloaded digest roots remain the executable connector path.

Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
Assisted-by: AI
@tnunamak
tnunamak merged commit 55d70c5 into integration/unified-stack Sep 16, 2026
12 of 15 checks passed
@tnunamak
tnunamak deleted the feat/docker-connectors-from-catalog branch September 16, 2026 23:14
@tnunamak

Copy link
Copy Markdown
Contributor Author

Folded into #141. Assisted-by: AI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant