1/**
2 * Email Routing is scoped separately from the rest of the Cloudflare API.
3 * A credential without it — notably Cloudflare OAuth, which carries no
4 * Email Routing scope at all — is refused before any resource logic runs:
5 *
6 * Unauthorized: Authentication error
7 * at provider.create (packages/alchemy/src/Apply.ts)
8 *
9 * Every suite below drives real Email Routing resources (routing settings,
10 * rules, catch-alls, destination addresses, sending subdomains) against the
11 * standing test zone, so all of them need the scope.
12 *
13 * Set `CLOUDFLARE_TEST_EMAIL_ROUTING=1` with an API-token credential that
14 * carries `Zone.Email Routing Rules` (edit) plus account-level
15 * `Email Routing Addresses` to run them.
16 */
17export const emailRoutingScoped = !!process.env.CLOUDFLARE_TEST_EMAIL_ROUTING;