fix(myorg-assistant): normalize GIT_REPO_URL host to git.rogi.casa in git-sync #27
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/gitsync-host-normalize"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
PR #26 added the
git-cloneinitContainer tomyorg-git-syncbut still trusted theGIT_REPO_URLsecret verbatim. The actual git-sync failure is the subdomain: the secret (and the clone URL it produces) points atgitea.rogi.casa, which returns Cloudflare 526 (origin unreachable). The working Gitea subdomain isgit.rogi.casa.Result: even with the initContainer,
git clone ${GIT_REPO_URL}hitgitea.rogi.casa-> 526 -> no/data/myorg/.git->Not a git repository.Fix
Normalize the
GIT_REPO_URLhost togit.rogi.casaat runtime (sed) inside the git-clone initContainer, so the clone succeeds regardless of the secret's stale host. Idempotent — if the secret is already correct, the sed is a no-op.Evidence
curl https://gitea.rogi.casa/-> HTTP 526 (Cloudflare)git ls-remote https://git.rogi.casa/...-> works (smart-HTTP reachable){namespace="myorg-assistant",pod=~"myorg-git-sync.+"}->Not a git repository: /data/myorgevery runRisk
Low. Single-line sed in an initContainer that already exists (from #26). No secret/volume/RBAC changes.
🤖 Generated by Hermes Platform Engineer
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.