| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/api/resources/workers_for_platforms | [Back] [Original] |
Whether the Workers in the namespace are executed in a trusted manner. When a Worker is trusted, it has access to the shared caches for the zone in the Cache API, and has access to the request.cf object on incoming Requests. When a Worker is untrusted, caches are not shared across the zone, and request.cf is undefined. By default, Workers in a namespace are untrusted.
Whether the Workers in the namespace are executed in a trusted manner. When a Worker is trusted, it has access to the shared caches for the zone in the Cache API, and has access to the request.cf object on incoming Requests. When a Worker is untrusted, caches are not shared across the zone, and request.cf is undefined. By default, Workers in a namespace are untrusted.
Whether the Workers in the namespace are executed in a trusted manner. When a Worker is trusted, it has access to the shared caches for the zone in the Cache API, and has access to the request.cf object on incoming Requests. When a Worker is untrusted, caches are not shared across the zone, and request.cf is undefined. By default, Workers in a namespace are untrusted.
Global CacheW configuration for the Worker. When caching is on,
the platform provisions a cloudflare.app zone for the Worker.
A type: worker entry in the exports map can override this
value for a single entrypoint.
Date indicating targeted support in the Workers runtime. Backwards incompatible fixes to the runtime following this date will not affect this Worker.
Flags that enable or disable certain features in the Workers runtime. Used to enable upcoming features or opt in or out of specific changes not included in a compatibility_date.
Declarative exports for the Workers most recent version,
including Durable Object classes (with their storage
backend) and named Worker entrypoints. Tombstoned lifecycle
entries are omitted, so only live exports (created and
expecting-transfer) are returned.
A named Worker entrypoint export (type: worker). Worker
entrypoints are always live (state: created) and carry no
storage or lifecycle fields. The optional cache block overrides
the Workers global cache_options.enabled for this entrypoint.
A live Durable Object export (state: created, the default). The
platform auto-provisions the namespace on first deploy, matches it
on subsequent deploys, and never mutates or deletes it as a side
effect of a code-only change. storage is required; renamed_to,
transferred_to and transfer_from are not allowed on a live
entry.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
A deleted tombstone: retires the provisioned namespace for this
class and all of its data. The class must be absent from the
uploaded code and no other Worker in the account may bind to the
namespace, otherwise the deploy is rejected. No other fields are
allowed. Deletion is irreversible.
A renamed tombstone: rewrites the provisioned namespaces class
name from this map key to renamed_to. The source class may stay
in code during the rollout window (an info notice is emitted).
storage, transferred_to and transfer_from are not allowed.
A transferred tombstone (source side of a two-phase transfer):
hands ownership of the provisioned namespace to another script in
the same account, named by transferred_to. The target must have
already deployed a matching expecting-transfer entry. The source
class may stay in code during the rollout window (an info notice
is emitted). storage, renamed_to and transfer_from are not
allowed.
The target side of a two-phase transfer (state: expecting-transfer). Declares that this script expects to receive
a namespace for this class from the transfer_from script. This
is a live entry, not a tombstone: bindings resolve through the
sources namespace until the source commits with a transferred
tombstone. storage and transfer_from are required; renamed_to
and transferred_to are not allowed.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
The tag of the Durable Object migration that was most recently applied for this Worker.
Named exports, such as Durable Object class implementations and named entrypoints.
Observability settings for the Worker.
The sampling rate for incoming requests. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Log settings for the Worker.
Whether invocation logs are enabled for the Worker.
Trace settings for the Worker.
The sampling rate for traces. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Controls how inbound trace context (traceparent/tracestate) headers on incoming requests are handled. authenticated (default) honors inbound trace context only when accompanied by a valid trace auth token. accept unconditionally accepts inbound trace context. Requires the trace propagation feature to be enabled.
Configuration for Smart Placement. Specify mode=smart for Smart Placement, or one of region/hostname/host.
Enables Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
Array of placement targets (currently limited to single target).
The last time the script was analyzed for Smart Placement.
Status of Smart Placement.
Script and version settings for Workers for Platforms namespace scripts. Same as script-and-version-settings-item but without annotations, which are not supported for namespace scripts.
List of bindings attached to a Worker. You can find more about bindings on our docs: https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/#bindings.
The jurisdiction of the R2 bucket.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
Global CacheW configuration for the Worker. When caching is on,
the platform provisions a cloudflare.app zone for the Worker.
A type: worker entry in the exports map can override this
value for a single entrypoint.
Date indicating targeted support in the Workers runtime. Backwards incompatible fixes to the runtime following this date will not affect this Worker.
Flags that enable or disable certain features in the Workers runtime. Used to enable upcoming features or opt in or out of specific changes not included in a compatibility_date.
Declarative exports for the Worker. Worker entrypoint entries
(type: worker) carry cache configuration for that entrypoint.
A named Worker entrypoint export (type: worker). Worker
entrypoints are always live (state: created) and carry no
storage or lifecycle fields. The optional cache block overrides
the Workers global cache_options.enabled for this entrypoint.
A live Durable Object export (state: created, the default). The
platform auto-provisions the namespace on first deploy, matches it
on subsequent deploys, and never mutates or deletes it as a side
effect of a code-only change. storage is required; renamed_to,
transferred_to and transfer_from are not allowed on a live
entry.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
A deleted tombstone: retires the provisioned namespace for this
class and all of its data. The class must be absent from the
uploaded code and no other Worker in the account may bind to the
namespace, otherwise the deploy is rejected. No other fields are
allowed. Deletion is irreversible.
A renamed tombstone: rewrites the provisioned namespaces class
name from this map key to renamed_to. The source class may stay
in code during the rollout window (an info notice is emitted).
storage, transferred_to and transfer_from are not allowed.
A transferred tombstone (source side of a two-phase transfer):
hands ownership of the provisioned namespace to another script in
the same account, named by transferred_to. The target must have
already deployed a matching expecting-transfer entry. The source
class may stay in code during the rollout window (an info notice
is emitted). storage, renamed_to and transfer_from are not
allowed.
The target side of a two-phase transfer (state: expecting-transfer). Declares that this script expects to receive
a namespace for this class from the transfer_from script. This
is a live entry, not a tombstone: bindings resolve through the
sources namespace until the source commits with a transferred
tombstone. storage and transfer_from are required; renamed_to
and transferred_to are not allowed.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
Summary of the declarative exports reconciliation that ran on
this upload. Populated only when the uploaded metadata included
an exports block. Durable Object entries drive reconciliation;
type: worker entries do not contribute to this summary.
Non-blocking info entries (stale tombstones, tombstone applied
with class still in code). See exports_reconciliation_info.
Stable, machine-readable tag identifying which reconciliation
scenario produced an error, warning, or info entry. Clients may
branch on this value instead of parsing message.
Source class names whose tombstone entry is now stale and safe
to delete from exports (no remaining referencing scripts).
Phase-1 transfer hints recorded on the target side.
Non-blocking warnings. See exports_reconciliation_warning.
Stable, machine-readable tag identifying which reconciliation
scenario produced an error, warning, or info entry. Clients may
branch on this value instead of parsing message.
Migrations to apply for Durable Objects associated with this Worker.
A single set of migrations to apply.
A list of classes to delete Durable Object namespaces from.
A list of classes to create Durable Object namespaces with SQLite from.
Tag used to verify against the latest migration tag for this Worker. If they dont match, the upload is rejected.
Tag used to verify against the latest migration tag for this Worker. If they dont match, the upload is rejected.
Migrations to apply in order.
A list of classes to delete Durable Object namespaces from.
A list of classes to create Durable Object namespaces with SQLite from.
Observability settings for the Worker.
The sampling rate for incoming requests. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Log settings for the Worker.
Whether invocation logs are enabled for the Worker.
Trace settings for the Worker.
The sampling rate for traces. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Controls how inbound trace context (traceparent/tracestate) headers on incoming requests are handled. authenticated (default) honors inbound trace context only when accompanied by a valid trace auth token. accept unconditionally accepts inbound trace context. Requires the trace propagation feature to be enabled.
Configuration for Smart Placement. Specify mode=smart for Smart Placement, or one of region/hostname/host.
Script and version settings for Workers for Platforms namespace scripts. Same as script-and-version-settings-item but without annotations, which are not supported for namespace scripts.
List of bindings attached to a Worker. You can find more about bindings on our docs: https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/#bindings.
The jurisdiction of the R2 bucket.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
Global CacheW configuration for the Worker. When caching is on,
the platform provisions a cloudflare.app zone for the Worker.
A type: worker entry in the exports map can override this
value for a single entrypoint.
Date indicating targeted support in the Workers runtime. Backwards incompatible fixes to the runtime following this date will not affect this Worker.
Flags that enable or disable certain features in the Workers runtime. Used to enable upcoming features or opt in or out of specific changes not included in a compatibility_date.
Declarative exports for the Worker. Worker entrypoint entries
(type: worker) carry cache configuration for that entrypoint.
A named Worker entrypoint export (type: worker). Worker
entrypoints are always live (state: created) and carry no
storage or lifecycle fields. The optional cache block overrides
the Workers global cache_options.enabled for this entrypoint.
A live Durable Object export (state: created, the default). The
platform auto-provisions the namespace on first deploy, matches it
on subsequent deploys, and never mutates or deletes it as a side
effect of a code-only change. storage is required; renamed_to,
transferred_to and transfer_from are not allowed on a live
entry.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
A deleted tombstone: retires the provisioned namespace for this
class and all of its data. The class must be absent from the
uploaded code and no other Worker in the account may bind to the
namespace, otherwise the deploy is rejected. No other fields are
allowed. Deletion is irreversible.
A renamed tombstone: rewrites the provisioned namespaces class
name from this map key to renamed_to. The source class may stay
in code during the rollout window (an info notice is emitted).
storage, transferred_to and transfer_from are not allowed.
A transferred tombstone (source side of a two-phase transfer):
hands ownership of the provisioned namespace to another script in
the same account, named by transferred_to. The target must have
already deployed a matching expecting-transfer entry. The source
class may stay in code during the rollout window (an info notice
is emitted). storage, renamed_to and transfer_from are not
allowed.
The target side of a two-phase transfer (state: expecting-transfer). Declares that this script expects to receive
a namespace for this class from the transfer_from script. This
is a live entry, not a tombstone: bindings resolve through the
sources namespace until the source commits with a transferred
tombstone. storage and transfer_from are required; renamed_to
and transferred_to are not allowed.
Durable Object storage backend. sqlite is the recommended (and
only) backend for new namespaces. legacy-kv is accepted only for
a class whose namespace already exists as KV-backed; the exports
flow never provisions a new legacy-kv namespace.
Summary of the declarative exports reconciliation that ran on
this upload. Populated only when the uploaded metadata included
an exports block. Durable Object entries drive reconciliation;
type: worker entries do not contribute to this summary.
Non-blocking info entries (stale tombstones, tombstone applied
with class still in code). See exports_reconciliation_info.
Stable, machine-readable tag identifying which reconciliation
scenario produced an error, warning, or info entry. Clients may
branch on this value instead of parsing message.
Source class names whose tombstone entry is now stale and safe
to delete from exports (no remaining referencing scripts).
Phase-1 transfer hints recorded on the target side.
Non-blocking warnings. See exports_reconciliation_warning.
Stable, machine-readable tag identifying which reconciliation
scenario produced an error, warning, or info entry. Clients may
branch on this value instead of parsing message.
Migrations to apply for Durable Objects associated with this Worker.
A single set of migrations to apply.
A list of classes to delete Durable Object namespaces from.
A list of classes to create Durable Object namespaces with SQLite from.
Tag used to verify against the latest migration tag for this Worker. If they dont match, the upload is rejected.
Tag used to verify against the latest migration tag for this Worker. If they dont match, the upload is rejected.
Migrations to apply in order.
A list of classes to delete Durable Object namespaces from.
A list of classes to create Durable Object namespaces with SQLite from.
Observability settings for the Worker.
The sampling rate for incoming requests. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Log settings for the Worker.
Whether invocation logs are enabled for the Worker.
Trace settings for the Worker.
The sampling rate for traces. From 0 to 1 (1 = 100%, 0.1 = 10%). Default is 1.
Controls how inbound trace context (traceparent/tracestate) headers on incoming requests are handled. authenticated (default) honors inbound trace context only when accompanied by a valid trace auth token. accept unconditionally accepts inbound trace context. Requires the trace propagation feature to be enabled.
Configuration for Smart Placement. Specify mode=smart for Smart Placement, or one of region/hostname/host.
A binding to allow the Worker to communicate with resources.
The jurisdiction of the R2 bucket.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
A secret value accessible through a binding.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
A secret value accessible through a binding.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
A secret value accessible through a binding.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
Map of secret names to secret metadata for resulting secrets.
Algorithm-specific key parameters. Learn more.
Data format of the key. Learn more.
Allowed operations with the key. Learn more.
Key data in JSON Web Key format. Required if format is jwk.
| Web Proxy Viewer | New URL | Original Page |