AA-BTS · Cloudflare
Cloudflare estate
A generated catalog of what is actually deployed, joined to the repos that deploy it, with health findings surfaced on top.
- Pages projects
- 30 Pages projects
- Workers
- 67 Workers
- On Actions
- 27/30
- Repos in org
- 1615
Findings
-
critical
cannot_deployNo usable deploy path: the git binding is stale or wiped and no Actions workflow is present. The project cannot ship without a manual wrangler run. 3 -
warn
stale_git_bindingCloudflare git binding still points at the frozen AA-PDCOE org. Pushes do not deploy, because the shared GitHub App lost its OAuth token in the 5 Oct migration. 26 -
warn
stale_productionNo PRODUCTION deployment within the last 90 days. Measured from Cloudflare's canonical deployment, not the latest of any environment — a preview deploy must not make a stale production look fresh. 4 -
warn
no_deploy_workflowRepo has no .github/workflows/deploy.yml, so deployment is manual. 3 -
info
missing_cfp_topicRepo is not tagged cfp, so Pages projects are not discoverable from the GitHub side. 30 -
info
template_version_driftCaller pins an older tag of cloudflare-deploy-templates than the newest release. 27 -
info
dual_deploy_pathProject has both an Actions workflow and a stale Cloudflare git binding. Inert: the account's GitHub App token is invalid, and the binding points at the old AA-PDCOE repo rather than the migrated one. Unbind at leisure; it becomes a real risk only if the App is reinstalled and someone pushes to the old org. 23 -
info
dashboard_deployLast deployment came from the Cloudflare dashboard rather than from code, so the deployed state may not match any commit. 5 -
info
binding_wipedGit binding has been cleared. Note this is NOT a side effect of Direct Upload — projects onboarded in batch 1 kept their binding — so a null binding predates or is independent of onboarding. 4 -
info
prod_not_onboardedDeploy workflow is present and has run, but production is still served by a deployment that did not come from it. Expected between merging to the integration branch and promoting to prod. 3
How Pages projects deploy
| Method | Projects |
|---|---|
| actions | 27 |
| cf_git | 3 |