feat(hlcc): dispatch approved deployments by explicit signal
This commit is contained in:
parent
357ac5e67a
commit
5897eb6850
13 changed files with 270 additions and 11 deletions
13
deployment/HLCC-PUSH-TO-DEPLOY-EVENT-PROTOCOL.hdlp
Normal file
13
deployment/HLCC-PUSH-TO-DEPLOY-EVENT-PROTOCOL.hdlp
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
# HLCC-PUSH-TO-DEPLOY-EVENT-PROTOCOL
|
||||
|
||||
状态:本地实现候选,尚未部署
|
||||
|
||||
语言层在冰朔明确确认“该提交需要部署”后,主动发出 `guanghu.deployment-intent/v1`。推送本身不会产生部署事件。意图必须绑定:
|
||||
|
||||
- 代码频道仓库、分支和完整提交 SHA;
|
||||
- `REQUEST-ID@完整提交SHA` 的不可变资源;
|
||||
- `deployment/requests/` 下的部署清单。
|
||||
|
||||
语言人格体通过 `/api/deployment/dispatch` 派发这一意图;接口要求一张单独的 `server-ops / dispatch-approved-deployment` 工单,且资源必须为同一 `REQUEST-ID@完整提交SHA`。服务端才写入 `guanghu.deployment-event/v1` 到本机队列。常驻部署 Agent 订阅此队列,读取同一提交中的清单,执行备份、部署、健康检查与回滚,并将回执回写到原工单。
|
||||
|
||||
没有部署意图的提交照常入库,回执为 `not_requested`;无效意图回执为 `rejected`,不会部署。推送工单绝不扩大为部署权限;服务器也不扫描仓库主动拉取部署。
|
||||
Loading…
Reference in a new issue