redis

Use the @bijection/connectors/redis entrypoint to declare redis resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Resource	Mode	Description
stream	`messages`	messages

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

stream

messages: messages

The following example matches configuration standard.

import { redis } from "@bijection/connectors/redis";
import { v } from "bijection/values";
const schema = { id: v.string() };
export const source = redis.stream.messages({ schema });

Inferred record types

{
  "messageId": string;
  "data": { id: string; };
}

Configuration: standard

Case: redis/stream/messages/standard. Connection and resource configuration are declared by this exact case. Credential kind: redis. Keep credential material in the private credential inventory.

Setting	Type	Required	Owner
`stream`	string	Yes	Resource binding
`endpoint`	string	Yes	Shared connection
`identityKey`	string	Yes	Resource binding
`database`	number	No	Shared connection

Complete configuration contract

{
  "setup": [],
  "resource": {
    "access": {},
    "defaults": {},
    "connector": "redis",
    "output": {
      "kind": "single",
      "collection": "records"
    },
    "credential_kind": "redis",
    "connection_fields": [
      "endpoint",
      "database"
    ]
  },
  "connection_setup": {
    "type": "object",
    "value": {
      "stream": {
        "fieldType": {
          "type": "string"
        },
        "optional": false
      },
      "endpoint": {
        "fieldType": {
          "type": "string"
        },
        "optional": false
      },
      "identityKey": {
        "fieldType": {
          "type": "string"
        },
        "optional": false
      },
      "database": {
        "fieldType": {
          "type": "number"
        },
        "optional": true
      }
    }
  },
  "execution": null
}

Native admission analysis is available for this exact declaration. Collection: records

Contract	Meaning
Initial	No initial acquisition
Changes	Delivered message occurrences
Deletions	Deletion detection unsupported
Resume	Opaque cursor
Gap	Explicit repair required after a gap
Retention	Unspecified

Complete native profile

{
  "movement": {
    "exchanges": {},
    "nativeInputLimitBytes": "0",
    "steps": [
      {
        "id": "acquire.1",
        "inputs": [],
        "action": {
          "operation": "acquire",
          "subject": "native input",
          "limitBytes": "0"
        }
      },
      {
        "id": "retain.1",
        "inputs": [
          "acquire.1"
        ],
        "action": {
          "operation": "retain",
          "subject": "acquisition evidence",
          "reason": "recovery",
          "release": "acquisition_custody"
        }
      },
      {
        "id": "interpret.1",
        "inputs": [
          "retain.1"
        ],
        "action": {
          "operation": "interpret",
          "subject": "acquired input",
          "produces": "records"
        }
      },
      {
        "id": "materialize.1",
        "inputs": [
          "interpret.1"
        ],
        "action": {
          "operation": "materialize",
          "subject": "source rows",
          "reason": "serving",
          "release": "replacement"
        }
      },
      {
        "id": "publish.1",
        "inputs": [
          "materialize.1"
        ],
        "action": {
          "operation": "publish",
          "subject": "source rows",
          "visibility": "with_acquisition"
        }
      }
    ]
  },
  "initial": "none",
  "changes": "delivered_messages",
  "deletions": "unsupported",
  "resume": "opaque_cursor",
  "retentionMs": null,
  "gap": "explicit_repair",
  "limits": {
    "exchange_evidence_bytes": "524288",
    "publication_page_records": "128",
    "record_fields": "32"
  },
  "restrictions": [
    "Message custody is distinct from current entity state and provider deletion"
  ],
  "commands": {}
}

Commands, occurrences and artifacts

{
  "records": {
    "records": {
      "protocol": "record_observation",
      "coverage": "records",
      "consistency": "observations",
      "atomicity": "record",
      "history": "observations",
      "recordRefresh": false,
      "reconciliation": false,
      "notifications": false,
      "snapshotMaxRows": null,
      "profile": {
        "movement": {
          "exchanges": {},
          "nativeInputLimitBytes": "0",
          "steps": [
            {
              "id": "acquire.1",
              "inputs": [],
              "action": {
                "operation": "acquire",
                "subject": "native input",
                "limitBytes": "0"
              }
            },
            {
              "id": "retain.1",
              "inputs": [
                "acquire.1"
              ],
              "action": {
                "operation": "retain",
                "subject": "acquisition evidence",
                "reason": "recovery",
                "release": "acquisition_custody"
              }
            },
            {
              "id": "interpret.1",
              "inputs": [
                "retain.1"
              ],
              "action": {
                "operation": "interpret",
                "subject": "acquired input",
                "produces": "records"
              }
            },
            {
              "id": "materialize.1",
              "inputs": [
                "interpret.1"
              ],
              "action": {
                "operation": "materialize",
                "subject": "source rows",
                "reason": "serving",
                "release": "replacement"
              }
            },
            {
              "id": "publish.1",
              "inputs": [
                "materialize.1"
              ],
              "action": {
                "operation": "publish",
                "subject": "source rows",
                "visibility": "with_acquisition"
              }
            }
          ]
        },
        "initial": "none",
        "changes": "delivered_messages",
        "deletions": "unsupported",
        "resume": "opaque_cursor",
        "retentionMs": null,
        "gap": "explicit_repair",
        "limits": {
          "exchange_evidence_bytes": "524288",
          "publication_page_records": "128",
          "record_fields": "32"
        },
        "restrictions": [
          "Message custody is distinct from current entity state and provider deletion"
        ],
        "commands": {}
      }
    }
  },
  "occurrences": null,
  "artifacts": {
    "raw_archive": false,
    "native_file_transfer_limit_bytes": null,
    "external_versions": false,
    "files": {}
  },
  "commands": {}
}

Recorded checks

Requirement	Scope	Evidence	Result
page-publication-recovery	{“kind”:“collection”,“name”:“records”}	This resource is inventoried from its executable declaration. No case-scoped check receipt is attached; historical provider observations do not qualify this configuration.	Execution result unavailable

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 in native.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.

Get Started

Use-case atlas

Platform

Data and Operations

Guides

Client Libraries

Tools

API Reference

Availability

Resources and modes

stream

messages: messages

Configuration: standard

Provider guidance

Provider references

Source and evidence

​Availability

​Resources and modes

​stream

​messages: messages

​Configuration: standard

​Provider guidance

​Provider references

​Source and evidence

Availability

Resources and modes

stream

messages: messages

Configuration: standard

Provider guidance

Provider references

Source and evidence