Skip to content

Cloudflare deploy: a Worker that sends a new consent field breaks keyrings starting on the old container during rollout #149

Open

Description

@jerryfane

Seen deploying #148 (2026-11-14 11:12–11:17Z). wrangler deploy switches the Worker at once, but the container rollout (v16→v17) takes minutes. The new Worker sent return_origins in consent settings; a keyring created on a still-v16 container answered 400 invalid JSON: unknown field "return_origins" (the binary decodes with DisallowUnknownFields). An existing keyring restarting on v16 would fail its PUT /consent the same way.

Mitigated by rolling the Worker back (the container app stays on the new image) and rolling forward once the rollouts API said completed. Receipt: /root/fleet-tools/state/phobos-dev/keyring-deploy-return-20261114/RECEIPT.md.

Options: (a) document a two-step deploy for any new consent/template field (image first with the var empty, then set the var after the rollout completes); (b) the Worker only sends optional fields when the container reports support (e.g. a version/capabilities field on an admin call).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions