fix(api): include momo backup script in runtime image
Some checks failed
CD Pipeline / tests (push) Successful in 1m19s
Code Review / ai-code-review (push) Successful in 24s
CD Pipeline / build-and-deploy (push) Successful in 3m59s
CD Pipeline / post-deploy-checks (push) Has been cancelled

This commit is contained in:
Your Name
2026-05-31 15:39:26 +08:00
parent 5bd5e7e49f
commit ebd9ca865f
2 changed files with 6 additions and 0 deletions

View File

@@ -22,9 +22,13 @@
# scripts/ 大部分不需要進 image僅白名單 production runtime/ops 種子腳本
# 2026-04-12 ogt (ADR-073 P2-1): 白名單允許 cron_km_vectorize.py
# 2026-05-13 codex: 白名單 T16 auto-repair canary PlayBook seed script
# 2026-05-31 codex: MOMO backup Ansible playbook copies the backup script from
# the controller image; keep only this backup script in the runtime context.
scripts/**
!scripts/
!scripts/cron_km_vectorize.py
!scripts/backup/
!scripts/backup/backup-momo-188-pg.sh
!scripts/ops/
!scripts/ops/awooop-seed-auto-repair-canary-playbook.py

View File

@@ -19,6 +19,8 @@ on:
- '.dockerignore'
# Dockerfile COPY scripts/ into the API image; keep production ops
# seed scripts deploy-coupled instead of repo-only.
- 'scripts/backup/backup-momo-188-pg.sh'
- 'scripts/ops/notify-awoooi-ops.sh'
- 'scripts/ops/awooop-seed-auto-repair-canary-playbook.py'
# Workflow-only changes do not rebuild runtime images. Use workflow_dispatch
# when an operator explicitly wants to test the CD pipeline itself.