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.
Herkunft
- Inhalts-Digest
- sha256:33795613d6999bd2b2a614c8ad5b567370bb565199561502e64dd58f7e8f21d9
- Veröffentlicht
- 2026-11-10T10:17:01Z
- Signaturidentität
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signatur
- Offiziellapplication/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
Referenz zu dieser Version
oci://hub.aggrega.ai/feature/core/compose-bridge:1.0.0- Gilt für
- —
- Steht in Konflikt mit
- —
Entwicklerparameter
Werte, die der Entwickler beim Anbinden dieser Funktion festlegt.
Erweitert BaseComponents#/schemas/BaseFeatureParameter
Ausgabevertrag
Werte, die diese Funktion an Konsumenten veröffentlicht.
Keine Ausgabewerte deklariert.
Annotationen
Keine Annotationen deklariert.
Beziehungen
Typisierte Kanten zu und von anderen veröffentlichten Entitäten. Eine Referenz ohne veröffentlichtes Ziel wird als unterbrochene Kante statt als Link dargestellt.
Verwendet
- $referweitert Schema (values)
BaseComponents#/schemas/BaseFeatureParameter
Verwendet von
implementiert