Enable provisioning by default

[penalosa]

Fixes DEVX-1557

This PR turns on the --x-provision flag by default.

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: tracked in DEVX-1585
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: not a stable v3 feature

[changeset-bot]

🦋 Changeset detected

Latest commit: 19ac2d4

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11030

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11030

miniflare

npm i https://pkg.pr.new/miniflare@11030

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11030

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11030

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11030

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11030

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11030

wrangler

npm i https://pkg.pr.new/wrangler@11030

commit: 19ac2d4

[github-actions]

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main penalosa/provision-by-default might be a good starting point.

Notes:

• your PR branch should be named v3-backport-11030
• add the skip-v3-pr label to the current PR to stop this workflow from failing

[petebacondarwin]

I wonder if we should bother writing to a redirected config at all? It is not a user editable file (normally), it is usually generated by a build too, and so will end up being recreated without the provisioned info anyway.

[penalosa]

I wonder if we should bother writing to a redirected config at all? It is not a user editable file (normally), it is usually generated by a build too, and so will end up being recreated without the provisioned info anyway.

I'm not sure I understand what you mean? This PR shouldn't write to the redirected config, I don't think

[petebacondarwin]

I wonder if we should bother writing to a redirected config at all? It is not a user editable file (normally), it is usually generated by a build too, and so will end up being recreated without the provisioned info anyway.

I'm not sure I understand what you mean? This PR shouldn't write to the redirected config, I don't think

Oops I misread the code. I saw the logic that said it didn't write to the user's config file but I made the incorrect assumption that it would write to the redirected one.

Alll good!