Add unsafe.containers

[emily-shen]

Add an unsafe.containers field to allow internal users to configure container options that we do not want to expose publicly (yet).

This will skip wrangler-side validation, and all validation will be done by the containers control plane, which will check if everything is the right shape and you have the right capabilities to do whatever it is you're trying to do.

{
  ...
  containers: [ {..., name: "my-container"}],
  unsafe: {
    containers: [ 
      {
        name: "my-container", // necessary to link it to the right container
        configuration: { 
           network: { 
              foo: "bar"
           }
        }
       }],
  }
  ...
}

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: internal
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: containers was new in v4

[changeset-bot]

🦋 Changeset detected

Latest commit: 6d016d5

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11233

wrangler

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

commit: 6d016d5

[petebacondarwin]

Would this be simpler to just put an unsafe property within each container section?

{
  ...
  containers: [
    {
      ...,
      name: "my-container"
      unsafe: {
        configuration: { 
           network: { 
              foo: "bar"
           }
        }
    }
  ],
  ...
}

Previously unsafe stuff was independent of bindings that are already in place. E.g. new experimental bindings or internal metadata to send up alongside the Worker.

[petebacondarwin]

Go for it!
It's a shame that we can't do the merge at an earlier stage in the configuration validation, which would be cleaner and simpler, but I understand that the intermediate typings and transforms that are necessary don't support the fields that can appear in the unsafe field.