Add option to make newly created resources remote

[penalosa]

Fixes https://jira.cfdata.org/browse/DEVX-2200

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s): Update binding creation commands cloudflare-docs#25535
  • Documentation not necessary because: this behaviour is interactive and self-documenting
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: not a v3 feature

[changeset-bot]

🦋 Changeset detected

Latest commit: 1bdcfa3

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

This PR includes changesets to release 3 packages

Name	Type
wrangler	Minor
@cloudflare/vite-plugin	Major
@cloudflare/vitest-pool-workers	Patch

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@10710

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

wrangler

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

commit: 1bdcfa3

[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/surface-remote-bindings might be a good starting point.

Notes:

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

[dario-piotrowicz]

LGTM 🙂

[petebacondarwin]

I feel that for any interactive prompt there should be a command line arg that can be used to avoid having to answer the prompt.

Currently, the only way to opt-out of most prompts is to run in non-interactive mode. But this is a heavy (and non-intuitive) hammer, since it doesn't allow fine grained control (you have to accept all the defaults).

I know that we don't do this for most prompts, but I think we should. And perhaps start here?

[petebacondarwin]

CI failures look legit

[petebacondarwin]

Love it!

[petebacondarwin]

On the documentation front, do we need to, now, update the command options in cloudflare-docs?

[penalosa]

@petebacondarwin potentially? But I'd quite like to see if the new docs generation can work here, which will need this to be released first. I'll make a docs issue