Enable auth-service/api-gateway on production, build their images in CI
This commit is contained in:
@@ -1,9 +1,12 @@
|
||||
"""Point the k3s practice cluster's ArgoCD Application at a freshly-built
|
||||
image tag, then trigger an immediate sync.
|
||||
"""Point the k3s ArgoCD Application at an image tag, then trigger an
|
||||
immediate sync.
|
||||
|
||||
Only touches `medical-chatbot-app` on the practice cluster
|
||||
(argocd.realvuxbaro.me). Never touches production — the EC2 Compose
|
||||
deployment isn't ArgoCD-managed at all.
|
||||
`medical-chatbot-app` (argocd.realvuxbaro.me) is the production Application —
|
||||
it serves both realvuxbaro.me and readytochat.realvuxbaro.me — since the
|
||||
2026-08-17 cutover. This script does not distinguish "forward" from
|
||||
"rollback": it points the Application at whatever IMAGE_TAG it is given and
|
||||
syncs, so `rollback-k3s.yml` reuses it unchanged with an older tag rather than
|
||||
duplicating this logic.
|
||||
|
||||
Required env: ARGOCD_PRACTICE_URL, ARGOCD_PRACTICE_PASSWORD, IMAGE_TAG.
|
||||
"""
|
||||
|
||||
Reference in New Issue
Block a user