Under the hood Bindings

How Devflare wires Secrets Store from config to runtime

Secrets Store bindings let Workers read account-level secrets without storing secret values in code.

Secrets Store compiles from to Wrangler , with local/test behavior called out explicitly.

Use this page when you need emitted config, preview behavior, or Cloudflare-specific limits. The overview and example pages stay focused on everyday app code.

Normalization: Devflare normalizes before emitting Wrangler
Compile target: Wrangler
Preview note: Cloudflare owns remote account secret provisioning and sync; Devflare reads only project-local secret values unless you deploy or test against Cloudflare.

How authored config becomes Wrangler config

The authored config stays camelCase and project-oriented. The compiler translates that into the Wrangler keys Cloudflare expects.

The emitted output is shown here so the usage pages do not have to explain compiler details.

Secrets Store config and emitted Wrangler output

Use this when you need to check how the Devflare config becomes Wrangler-compatible config.

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'secret-worker',

secretsStoreId: 'store-123',

bindings: {

secretsStore: {

API_TOKEN: 'api-token',

STRIPE_WEBHOOK_SECRET: 'stripe-webhook-secret'

}

})

What local runtime support covers

Full local support through Miniflare wiring, local values, and explicit fixture values for pure tests
The default docs recipe uses or .
Pure unit tests can use / when the test only needs deterministic application behavior.

Compile, preview, and cleanup behavior

Devflare emits Wrangler from the native config surface.
Preview and deployment lifecycle stay feature-specific; do not assume all Cloudflare products can be created, cloned, or cleaned up the same way.
Cloudflare owns remote account secret provisioning and sync; Devflare reads only project-local secret values unless you deploy or test against Cloudflare.

Cloudflare docs vs the Devflare layer

Cloudflare Secrets Store docs is the platform reference. Use this internals page when you need to compare Cloudflare's product docs with Devflare config, generated env types, local support, and preview behavior for .

Reference

Cloudflare Secrets Store docs

Cloudflare Docs

Platform reference for secrets, account-level Secrets Store bindings, and secure Worker access.

Question	Cloudflare docs	This Devflare page
Primary focus	Platform reference for secrets, account-level Secrets Store bindings, and secure Worker access.	How to author , what the runtime surface looks like, and how Secrets Store fits a Devflare project.
Testing and runtime lens	Cloudflare’s docs focus on the raw binding API, product semantics, and platform limits for the binding itself.	Full local support through Miniflare wiring, local values, and explicit fixture values for pure tests. Use the Devflare guidance when you need the honest local harness or the right remote gate instead of only the product API shape.
When to open it	When you need the platform contract, limits, APIs, or account-level product details.	When you are wiring, testing, previewing, or reviewing the binding inside a Devflare app.

Secrets Store

Add the Secrets Store config, call from worker code, and start with the local test path Devflare supports.

Testing Secrets Store

Test Secrets Store by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.