docs(awooop): record t3 ansible deployment
This commit is contained in:
@@ -1919,7 +1919,12 @@ Phase 6 完成後
|
||||
**production 追加**:
|
||||
- Gitea `run-migration` run `1933`:`adr090d_ansible_operation_types.sql` 已成功套用,含 owner fallback。
|
||||
- 同 run 的 `Seed asset_discovery_run (audit)` 仍失敗;新根因是 unquoted heredoc 下 tools JSON literal 還寫成 `'{\"psql\": 1, \"gitea_ci\": 1}'::jsonb`,PostgreSQL 視為非法 JSON。
|
||||
- 後續修正:workflow tools JSON literal 改成 `'{"psql": 1, "gitea_ci": 1}'::jsonb`;仍需補寫本次 migration audit row,並用下一個 migration push 驗證 live gate。
|
||||
- 後續修正:workflow tools JSON literal 改成 `'{"psql": 1, "gitea_ci": 1}'::jsonb`。
|
||||
- 已補 production `asset_discovery_run` repair audit row(`ci_migration_manual_repair` / `commit_sha=ca80972dc73cb647f8fab3bf9439784c4b8eef7b`)。
|
||||
- Production DB constraint 已確認包含全部 `ansible_*` operation types。
|
||||
- CD 已部署 `ca80972d` image,deploy marker `07000dae`;API/Web/Worker rollout success。
|
||||
- B6C589 truth-chain smoke:`manual_required/blocked`、`mcp_gateway_total=8`、`execution.ansible.considered=false`、`records=0`、not_used_reason 清楚顯示沒有 Ansible audit record。
|
||||
- 下一個 migration push 仍需驗證 `run-migration` audit seed live gate,因本輪 workflow 修正後未再新增 migration 觸發重跑。
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user