Migrates backend/configs/hermes.py from the legacy url= form to the new remotes=[{name, url}, ...] form introduced by #3.
Important: the deploy target is admin/ansible (compose at poc/hermes/stack-compose.yml), not uber_backup as the old URL string suggested. The github.com/rudolf1/uber_backup URL was working only by accident — the brencher container is actually serving admin/ansible content from that repo name on github (which no longer exists as a public repo; brencher's old cached clone is what's been keeping hermes alive).
PR #27 (closed) had the wrong URL set — it pointed at the non-existent admin/uber_backup/hermes/uber_backup and included a broken github remote. The error was caught when comparing brencher's working clone (/tmp/hermes_606a8) against the file's URL: the clone was actually admin/ansible, not uber_backup.
Test plan
Add gitea_hermes/feat/migrate-hermes-to-multi-remote-v2 to brencher state for hermes.
Confirm hermes stack stays healthy (auto-7fa09102 is current; expected_version == actual_version after merge).
Merge this PR.
Closes#21
Refs #11 (parallel issue, same scope)
Part of #18
## Summary
Migrates `backend/configs/hermes.py` from the legacy `url=` form to the new `remotes=[{name, url}, ...]` form introduced by #3.
**Important**: the deploy target is `admin/ansible` (compose at `poc/hermes/stack-compose.yml`), not `uber_backup` as the old URL string suggested. The `github.com/rudolf1/uber_backup` URL was working only by accident — the brencher container is actually serving `admin/ansible` content from that repo name on github (which no longer exists as a public repo; brencher's old cached clone is what's been keeping `hermes` alive).
## What's in this PR
Same pattern as `hermes_infra.py` after PR #8:
```python
clone = GitClone(remotes=[
{"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/ansible"},
{"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/ansible"},
])
```
- `gitea_hermes`: where feature branches live (`hermes/ansible:*`)
- `gitea_admin`: the live-deploy source (`admin/ansible:*`)
- **No github remote** — brencher can't reach github through the proxy (HTTP 403 on CONNECT tunnel; see #23 for the same fix)
- `branchNamePrefix="ansible"` is dropped — it's a silent no-op when no remote is named `origin` (`backend/steps/git.py` ~L104)
## Diff
```diff
-clone = GitClone(url="https://github.com/rudolf1/uber_backup.git", branchNamePrefix="ansible")
+clone = GitClone(remotes=[
+ {"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/ansible"},
+ {"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/ansible"},
+])
```
## Supersedes
PR #27 (closed) had the wrong URL set — it pointed at the non-existent `admin/uber_backup`/`hermes/uber_backup` and included a broken `github` remote. The error was caught when comparing brencher's working clone (`/tmp/hermes_606a8`) against the file's URL: the clone was actually `admin/ansible`, not `uber_backup`.
## Test plan
1. Add `gitea_hermes/feat/migrate-hermes-to-multi-remote-v2` to brencher state for `hermes`.
2. Watch brencher logs: `Cloning repositories [gitea_hermes, gitea_admin]` should succeed (both remotes exist).
3. Confirm `hermes` stack stays healthy (`auto-7fa09102` is current; expected_version == actual_version after merge).
4. Merge this PR.
Closes #21
Refs #11 (parallel issue, same scope)
Part of #18
Migrates backend/configs/hermes.py from the legacy single-remote
url= form to the remotes=[{name, url}, ...] form introduced by #3.
The deploy target is admin/ansible (compose at poc/hermes/stack-compose.yml),
not uber_backup as the old URL string suggested. Mirrors the pattern in
backend/configs/hermes_infra.py after PR #8:
- gitea_hermes: where feature branches live (hermes/ansible:*)
- gitea_admin: the live-deploy source (admin/ansible:*)
No github remote: brencher container cannot reach github through the
proxy (HTTP 403 on CONNECT tunnel; see #23 for the same fix).
branchNamePrefix='ansible' is dropped — it's a no-op when no remote
is named 'origin' (backend/steps/git.py ~L104).
Closes#21
Refs #11 (parallel issue, same scope)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Migrates
backend/configs/hermes.pyfrom the legacyurl=form to the newremotes=[{name, url}, ...]form introduced by #3.Important: the deploy target is
admin/ansible(compose atpoc/hermes/stack-compose.yml), notuber_backupas the old URL string suggested. Thegithub.com/rudolf1/uber_backupURL was working only by accident — the brencher container is actually servingadmin/ansiblecontent from that repo name on github (which no longer exists as a public repo; brencher's old cached clone is what's been keepinghermesalive).What's in this PR
Same pattern as
hermes_infra.pyafter PR #8:gitea_hermes: where feature branches live (hermes/ansible:*)gitea_admin: the live-deploy source (admin/ansible:*)branchNamePrefix="ansible"is dropped — it's a silent no-op when no remote is namedorigin(backend/steps/git.py~L104)Diff
Supersedes
PR #27 (closed) had the wrong URL set — it pointed at the non-existent
admin/uber_backup/hermes/uber_backupand included a brokengithubremote. The error was caught when comparing brencher's working clone (/tmp/hermes_606a8) against the file's URL: the clone was actuallyadmin/ansible, notuber_backup.Test plan
gitea_hermes/feat/migrate-hermes-to-multi-remote-v2to brencher state forhermes.Cloning repositories [gitea_hermes, gitea_admin]should succeed (both remotes exist).hermesstack stays healthy (auto-7fa09102is current; expected_version == actual_version after merge).Closes #21
Refs #11 (parallel issue, same scope)
Part of #18
37616c5935to437e6ac034Migrates backend/configs/hermes.py from the legacy single-remote url= form to the remotes=[{name, url}, ...] form introduced by #3. The deploy target is admin/ansible (compose at poc/hermes/stack-compose.yml), not uber_backup as the old URL string suggested. Mirrors the pattern in backend/configs/hermes_infra.py after PR #8: - gitea_hermes: where feature branches live (hermes/ansible:*) - gitea_admin: the live-deploy source (admin/ansible:*) No github remote: brencher container cannot reach github through the proxy (HTTP 403 on CONNECT tunnel; see #23 for the same fix). branchNamePrefix='ansible' is dropped — it's a no-op when no remote is named 'origin' (backend/steps/git.py ~L104). Closes #21 Refs #11 (parallel issue, same scope)437e6ac034to94ca49b9a4Pull request closed