cloudflare

type APIError struct {
	Code    int
	Message string
}

type Account struct {
	ID   string `json:"id"`
	Name string `json:"name"`
}

type Asset struct {
	Path string // e.g. "/index.html", "/assets/index-abc.js"
	Body []byte
}

type Client struct {
	HTTP  *http.Client
	Token string
	Base  string // default https://api.cloudflare.com/client/v4
}

type DeployInput struct {
	AccountID         string
	ScriptName        string // "flue-relay"
	Module            []byte // the built worker, ESM
	CompatibilityDate string // "2026-08-01"

	// NewSQLiteClasses names Durable Object classes being introduced. It is
	// set on the first deploy and empty afterwards; Deploy also recovers on its
	// own when Cloudflare says the migration is already applied.
	//
	// These must be *SQLite* classes: the free plan offers no other storage
	// backend for Durable Objects, so a key-value migration would shut free
	// accounts out of the relay entirely.
	NewSQLiteClasses []string

	DOBindings           map[string]string // name -> class: {"HUB": "DaemonHub"}
	Assets               []Asset
	AssetsRunWorkerFirst []string // ["/daemon", "/client", "/api/*"]

	// PlainTextVars become bindings of type "plain_text": ordinary,
	// non-secret env vars the Worker can read. The relay's version stamp
	// travels this way. Values here are visible to anyone who can read the
	// script in the dashboard — nothing secret may ever ride one.
	PlainTextVars map[string]string

	// AssetHeaders is a `_headers` document — response headers for the static
	// assets, in the file format Cloudflare's asset router parses. Empty sends
	// no header config at all. See assetsConfig.Headers for why this travels in
	// the script metadata rather than as a file among the assets.
	//
	// It applies to responses the asset router produces, including the ones a
	// Worker asks for through its assets binding, and not to responses the
	// Worker constructs itself.
	AssetHeaders string

	// AssetsBinding is the name the Worker reads its static assets off env
	// under — "ASSETS" for the relay, matching `assets.binding` in
	// relay/wrangler.jsonc. It is emitted as a binding of type "assets".
	//
	// This is separate from attaching the assets at all, and the distinction is
	// easy to get wrong: the completion token in metadata.assets.jwt makes
	// Cloudflare's *router* serve the files, and that alone is enough for a
	// Worker that only ever needs static paths served for it. It does not
	// create env.<name>. A Worker that calls env.ASSETS.fetch(...) itself — as
	// the relay does, to fall through to the SPA on unmatched /api/* — needs
	// this binding too, or that call is on undefined at runtime.
	//
	// Empty means no binding, which is correct for a router-only deploy.
	AssetsBinding string

	// Observability turns on Workers Logs for the script, matching
	// `"observability": {"enabled": true}` in relay/wrangler.jsonc. Without it
	// a relay deployed by `flue relay setup` would have no logs to debug from
	// where a wrangler-deployed one would.
	Observability bool
}