[C3] Support template substitution in wrangler config files

[vicb]

This PR adds template substitution for the wrangler config files.

• <WORKER_NAME> is replaced with the worker name (from the project).
• <COMPATIBILITY_DATE> is replaced with the latest workerd date

This in in addition to how <TBD> is currently replaced by a context depend value (could be either the worker name or the compatibility date)

Notes:

• the new template substitution is applied before the legacy one to preserved backward compatibility.
• <WORKER_NAME> is needed to unblock Open Next (in a follow up PR)
• <COMPATIBILITY_DATE> is not currently used but will be used to make substitution clearer, see "Future work" below

For .json/.jsonc only the string values are considered.
For .toml it uses a simple string replace - which should be ok if we use uncommon key format.

Note / Future work:

We currently use this pattern for wrangler config / package.json:

{
	"name": "<TBD>",
	"main": "src/entry.py",
	"compatibility_date": "<TBD>",
	"compatibility_flags": ["python_workers"],
	"observability": {
		"enabled": true,
	},
}

IMO we should replace that with the mechanism of this PR for clarity, i.e.

{
	"name": "<WORKER_NAME>",
	"main": "src/entry.py",
	"compatibility_date": "<COMPATIBILITY_DATE>",
	"compatibility_flags": ["python_workers"],
	"observability": {
		"enabled": true,
	},
}

(We should keep the current logic for backward compatibility but update it and the templates)

---

• Tests
  • Tests included/updated
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: internal
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: c3

[changeset-bot]

🦋 Changeset detected

Latest commit: c9f28a0

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: c9f28a0

[petebacondarwin]

Great! To be honest, if we are going in this direction we should just get rid of the <TBD> placeholders. All of this is internal API and we have full control over it. Keeping TBD around just adds additional complexity and is confusing.

[vicb]

Great! To be honest, if we are going in this direction we should just get rid of the <TBD> placeholders. All of this is internal API and we have full control over it. Keeping TBD around just adds additional complexity and is confusing.

Doesn't c3 support external templates?
I would need to look if it coud be used there