chore(ci): retire the merge-time dev deploy — both hosts are Ansible-managed now #160
No reviewers
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot!160
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/retire-cd-dev-deploy"
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?
Closes the last loose end from the production migration (iac-repo#219).
Since 2026-08-01 both instances are deployed by
weatherbot-ansiblefrom/opt/weatherbot-svc, under the same compose project name (weatherbot) this job's checkout-rebuild used — so the next merge to main would have had CD silently revert dev to the pre-Ansible layout, and the two management planes would flip-flop on every merge vs. every play run.Running the Ansible play from CI instead was considered and rejected for the same reason
release.ymlholds no deploy credentials (#154): limiting the play to-l docker-testdoesn't limit the secret — decrypting the weatherbot vault requires the fleet-wide vault password, which unlocks every vault in the shared inventory.So
cd.ymlbecomes tests-only (renamed CI (main)), and rollouts are operator-run at release cadence, dev first — the same model as every other service in the fleet:vX.Y.Z→release.ymlpublishes the imageweatherbot_imagein iac-repoansible-playbook site.yml -l docker-test, soak, then-l docker-hostREADME pipeline table + release runbook updated to match.
DEV_SSH_KEY/DEV_HOSTare no longer read by anything and can be removed from Settings → Actions.🤖 Generated with Claude Code