Skip to main content
Use the @bijection/connectors/cloudflare entrypoint to declare Cloudflare 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.

Worker deployments

pull: Deployment observation

The following example matches configuration standard.

Configuration: standard

Case: cloudflare/deployments/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: cloudflare. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: deployments
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Worker invocations

query: Sampled invocation groups over a fixed window

The following example matches configuration standard.

Configuration: standard

Case: cloudflare/analytics/query/standard. Connection and resource configuration are declared by this exact case. Credential kind: cloudflare. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: invocations
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only observation feed. Cloudflare is not a system of record here: a deployment create has no idempotency key and applied a stale If-Match, so nothing here deploys, routes, promotes or deletes. The connection holds a cloudflare bearer credential (cloudflare.credential) for https://api.cloudflare.com. Bindings name the accountId and the Worker’s scriptName. Identity is the account id. deployments.pull lists the Worker’s deployments with their creation time, strategy, version split and message. Which deployment is current is not claimed. analytics.query reads per-minute invocation groups of the Worker over a closed window from GraphQL workersInvocationsAdaptive, the dataset that carries scriptVersion. These are sampled aggregates with no completeness flag: each group keeps its sampleInterval, the first non-empty read of a closed minute was not its final value, and a Worker subrequest counts one client request twice in zone traffic. A group missing from a later read is not withdrawn; nothing here is a ledger. Nothing here has run against Cloudflare or been qualified.

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.