Skip to content

Move the Cloudflare secrets into a production environment #45

Description

@jamesconwaydev

The Cloudflare token is a repository secret, so any workflow in the repo can read it. Putting it in a production environment that only main can deploy to means a workflow on another branch never sees it. While we're in there, the deploy's workflow_run trigger should also check that the run was on main.

This needs the token re-entered, so it's easiest to do alongside the next rotation.

Done when CLOUDFLARE_API_TOKEN and the account ID live only in the production environment, that environment allows main alone, and the deploy job checks head_branch == 'main'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: ciWorkflows, action pins, releases and deployspriority: mediumNext in line once the high ones are done

    Fields

    Area

    CI

    Priority

    Medium

    Effort

    S

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions