Minor Changes
-
#15792
479e1e8Thanks @flakey5! - Configure SSH for experimental Durable Object-managed ContainersSet
containers[].sshandcontainers[].authorized_keyswhen usingscheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration. -
#15779
fc3cbaaThanks @Naapperas! - Supportworkflowentries in theexportsconfiguration mapA Worker can now declare the Workflows it defines in
exports, keyed by theWorkflowEntrypointclass name:{ "exports": { "MyWorkflow": { "type": "workflow", "name": "my-workflow", "limits": { "steps": 100 }, "schedules": "0 * * * *" } } }A
workflowexport accepts the same settings as aworkflowsbinding:limits,concurrency,schedules, anddefault_retention.wrangler deployandwrangler versions uploadsend these entries to the upload API by name, andwrangler deployandwrangler triggers deployprovision the Workflow with its settings, just as they do forworkflowsbindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export.@cloudflare/configadds the matchingexports.workflow()helper. Local development does not yet act on these entries.