Feature
example/db-binding
A database-binding feature: attach it to an application component to wire that component to a stateful-server database and deliver the connection. The feature carries the `databases` uses-edge to the target plus the delivery declaration that lands the database's published host on the consumer's environment as ADMINER_DEFAULT_SERVER. The binding is the vehicle for the edge — the application component consumes the database through it, so the connection wiring is declared once as a reusable attachment rather than inline on every consumer. It renders no resource of its own — its FeatureRecipe (db-binding) is a no-op. Like any feature instance it still resolves to a FeatureRecipe; its whole contribution is the bound edge and its injection.
Provenance
- Content digest
- sha256:71ff9e2fc8ea666aaefbd5919089ae72451d913c7efb999a57390a2668b83464
- Published
- 2026-11-10T10:17:38Z
- 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:1ca68faacc1cd2a8aecf62bbf961c941ed1540e969d1dfc40018a1dfd28cb1fa
Reference at this version
oci://hub.aggrega.ai/feature/example/db-binding:1.0.0- Applies to
- —
- Conflicts with
- —
Developer parameters
Values the developer sets when attaching this feature.
No developer parameters declared.
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
This entity uses nothing in the catalog.
Used by
implements