Skip to content

[Workers] Mention Flagship in automatic provisioning docs #31990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ericclemmons wants to merge 4 commits into
base: production
Choose a base branch
from
+29 −1
Open

[Workers] Mention Flagship in automatic provisioning docs #31990

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9401ad1
[Workers] Mention Flagship in automatic provisioning docs
ericclemmons Jul 10, 2026
73a0ab9
[Workers] Keep Flagship provisioning update focused
ericclemmons Jul 10, 2026
073d98d
[Workers] Remove Flagship documentation link
ericclemmons Jul 10, 2026
422a922
[Workers, Flagship] Announce automatic provisioning
ericclemmons Jul 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Automatic provisioning for Flagship bindings
description: Wrangler can now automatically provision Flagship apps when deploying Workers with Flagship bindings.
products:
- workers
- flagship
date: 2026-07-09
---

import { WranglerConfig } from "~/components";

Wrangler automatic resource provisioning now supports Flagship bindings. Add a `flagship` binding without an `app_id`, and Wrangler can connect an existing Flagship app or create a new one during deployment. Wrangler writes the resulting `app_id` back to your configuration file.

<WranglerConfig>

```jsonc
{
"flagship": [
{
"binding": "FLAGS",
},
],
}
```

</WranglerConfig>

For more information, refer to [automatic provisioning](/workers/wrangler/configuration/#automatic-provisioning) and [Flagship bindings](/flagship/binding/).
2 changes: 1 addition & 1 deletion src/content/docs/workers/wrangler/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ Further, there are a few keys that can _only_ appear at the top-level.

Wrangler can automatically provision resources for you when you deploy your Worker without you having to create them ahead of time.

This currently works for KV, R2, and D1 bindings.
This currently works for KV, R2, D1, and Flagship bindings.

To use this feature, add bindings to your configuration file _without_ adding resource IDs, or in the case of R2, a bucket name. Resources will be created with the name of your worker as the prefix.

Expand Down