chore: delete render.yaml, the retired Render blueprint - #540
Merged
Merged
Conversation
Production moved to Google Cloud / GKE and Render became internal-only, but the blueprint stayed in the tree still defining ai-identity-api and ai-identity-gateway as web services for api.ai-identity.co and gateway.ai-identity.co. Those are the same two hostnames k8s/ingress.yaml routes to api-service and gateway-service behind the ai-identity-cert ManagedCertificate, so the tree held two deploy configs claiming the same hosts, and the stale one carried current-looking CORS_ORIGINS and GATEWAY_URL values. That is what made it deceptive rather than merely dead. Nothing consumed it: no workflow under .github/ mentions Render, and deploy-gke.yml is the deploy path. This is the first item of section 10.2 in docs/gcloud-migration-plan.md, now ticked. The pointers the deletion would otherwise have left dangling are fixed here too. scripts/keepalive_cron.py and scripts/keepalive.sh both told the reader to see render.yaml for configuration; they now record that the Render cron is retired and that scheduling is external. Left alone deliberately. The keepalive scripts have no scheduler anywhere in this repo, no k8s CronJob and no workflow referencing them, so items 2 and 3 of that same checklist, rewriting or deleting them, are a separate call. docs/gke-vs-cloudrun-evaluation.md keeps its mention of render.yaml, since it records a decision taken while the file existed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HYXvJjjD9YDRdHu1k4b68e
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Levaj2000
marked this pull request as ready for review
September 13, 2026 17:00
This was referenced Sep 13, 2026
Levaj2000
added a commit
that referenced
this pull request
Sep 14, 2026
) The sandbox network allowlist still named the retired Render host (ceo-agent-evfb.onrender.com; render.yaml was deleted in #540). The dashboard now answers at ceo.corethread.tech, which is where the persona routines post their briefings. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014c1RBLy2Kiinj7QnLCNi7N
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deletes
render.yamland repairs the pointers that deletion would otherwiseleave dangling.
Why it is stale, and why it was worse than merely dead
Production moved to Google Cloud / GKE and Render became internal-only, but
the blueprint stayed in the tree still defining
ai-identity-apiandai-identity-gatewayas Render web services forapi.ai-identity.coandgateway.ai-identity.co, plus anai-identity-keepalivecron.Those are the same two hostnames
k8s/ingress.yamlroutes toapi-serviceand
gateway-servicebehind theai-identity-certManagedCertificate. So thetree carried two deploy configs claiming the same hosts, and the stale one
carried current-looking
CORS_ORIGINSandGATEWAY_URLvalues. Reading therepo cold, there was no way to tell which was live.
Nothing consumed it. No workflow under
.github/mentions Render;deploy-gke.ymlis the deploy path.
Checklist item
This is the first item of
docs/gcloud-migration-plan.mdsection 10.2 "CodeCleanup", which this PR ticks:
Dangling pointers, fixed here
scripts/keepalive_cron.pyandscripts/keepalive.shboth told the reader tosee
render.yamlfor configuration. They now record that the Render cron isretired and that scheduling is external.
Deliberately left alone
this repo: no
k8s/CronJob, no workflow references them. That makes items2 and 3 of the same checklist (
Delete scripts/keepalive_cron.py,Update scripts/keepalive.sh or remove it) a real decision rather than cleanup, sothey stay open for the maintainer.
docs/gke-vs-cloudrun-evaluation.mdkeeps its mention ofrender.yaml.It records a decision taken while the file existed, so rewriting it would
falsify the record rather than update it.
ARCHITECTURE hosting text, the UptimeRobot setup script) are untouched.
Verification
render.yamlremains:grep -rn 'render\.yaml'returnsonly the migration plan (now ticked) and the evaluation doc (historical).
python3 -m py_compileandruff checkclean onscripts/keepalive_cron.py;bash -nclean onscripts/keepalive.sh.LC_ALL=C grepfor non-print characters: zero across the changed files, sothe plain-ASCII sweep from docs(ocsf-audit): hold the pin at 5b76fa6, record praxis #84 e6756fe #536 still holds.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HYXvJjjD9YDRdHu1k4b68e
Generated by Claude Code