Feature

core/compose-bridge

Lets components sitting on different networks of one local compose file reach one another. On the local target a component joins the network of its compose file, or the one its boundary names with the aggrega.ai/namespace annotation: boundaries sharing one compose file without that annotation share one network, and the annotation is what separates them. An edge crossing between two networks has no route; attached at boundary scope, this renders one small proxy into the boundary's own compose file, joined to the networks of the crossing edges' ends, and rewrites each consumer's address so it reaches its target through that proxy. Only an edge whose two ends are assembled into that same file is relayed; a connection between two files is left as written. Every input is the operator's, so the operator attaches it in the Release, on the boundary holding the seam, under that boundary's features. Both the listening ports and the rewritten addresses are derived from the edges that actually cross, so no address is hand-authored: what a Release may set, in infra, is the base port a collision falls back to, and which published field is taken as the upstream address. It is a network-architecture concern rather than a per-component one, which is why it attaches to a boundary and gates on no component type.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:33795613d6999bd2b2a614c8ad5b567370bb565199561502e64dd58f7e8f21d9
Published
2026-11-10T10:17:01Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:4280d87fd952ad4b50fb183e0c80153aa51fb1e617ad67377108eb3846fb64e0

Reference at this version

oci://hub.aggrega.ai/feature/core/compose-bridge:1.0.0
Applies to
—
Conflicts with
—

Developer parameters

Values the developer sets when attaching this feature.

Extends BaseComponents#/schemas/BaseFeatureParameter

Output contract

Values this feature publishes to consumers.

No output values declared.

Annotations

No annotations declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Feature concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy