Skip to content

chore: partially migrate deployment to cf - #32857

Draft
MattieTK wants to merge 1 commit into
productionfrom
chore/partial-cf-migration
Draft

chore: partially migrate deployment to cf#32857
MattieTK wants to merge 1 commit into
productionfrom
chore/partial-cf-migration

Conversation

@MattieTK

Copy link
Copy Markdown
Member

Summary

Partially migrates the Cloudflare Docs Worker from Wrangler to the new cf CLI. Production now builds through the Cloudflare Vite plugin using cloudflare.config.ts and deploys the generated Build Output with cf deploy --prebuilt.

Wrangler remains only where equivalent high-level cf integration is not yet available: Workers test configuration, Worker type generation, and PR preview deployment packaging. The preview workflow currently relies on:

wrangler deploy \
  --config wrangler.preview.json \
  --dispatch-namespace preview-deployments \
  --name "<script-name>"

cf dispatch-namespaces scripts update <script-name> supports low-level Workers for Platforms uploads, but cf deploy does not accept a dispatch namespace or script name. Equivalent support should preserve cf deploy's Build Output, static asset, binding, compatibility, and observability handling while targeting the named namespace script.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/.github/ @cloudflare/content-engineering, @kodster28, @mvvmm, @colbywhite, @ahaywood, @MohamedH1998
* @cloudflare/product-owners
*.ts @cloudflare/content-engineering, @kodster28
*.js @cloudflare/content-engineering, @kodster28
package.json @cloudflare/content-engineering

@github-actions

Copy link
Copy Markdown
Contributor

@kodster28 kodster28 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just putting a placeholder here, definitely should discuss before we'd get close to merging any of this.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants