@bijection/connectors/mqtt entrypoint to declare mqtt resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
topic
messages: messages
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:mqtt/topic/messages/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: mqtt. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
telemetry
latest: latest
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:mqtt/telemetry/latest/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: mqtt. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
These recipes return ordinary typed resources or atomic resource groups. The registration innative.ts owns their callable factories, named modes and representative cases. Credentials, endpoints and physical resource selection belong to deployment bindings. Application schemas and message interpretation belong to the declaration. Acquisition and recovery guarantees come from native admission, not the mode name.
Each public resource has a case and explicit scoped evidence requirements. These registrations alone establish no executed provider checks or hosted qualification. The catalog reports missing execution evidence as unestablished. Native source inspection remains authoritative for the actual installation.
Protocol helpers such as HTTP request builders and generated operation descriptors are authoring primitives. They do not count as independently installable provider resources. External compute remains owned by its provider.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.