Expose the certified dataset SHA-256 and gate production on the served identity
维护者通常 1 天内回复
评估
调研方向
Start with gateway_models.py, the executor bundle and routing state to trace how the certified default dataset SHA-256 can reach PolicyEngineBundle. Then inspect /versions, cloud-run-simulation-entry-smoke.sh, and the policyengine-release updater. Done means deployed bundle identities are exposed and checked on candidate and promotion, and the updater verifies the dispatch identity against the installed wheel and records the digests in its PR.
由索引模型根据 Issue 内容生成。
描述
For the UK Autumn Budget (28 October 2026), every number the simulation API serves must be traceable to the exact certified policyengine.py bundle and dataset bytes. Production must also be confirmed to serve that bundle before it counts as ready. Today:
- The public
PolicyEngineBundleschema (gateway_models.py) carries model and data versions but no dataset SHA-256. /versionsreturns route maps only, with no per-bundle identity.- The deploy smoke (
cloud-run-simulation-entry-smoke.sh) checks only that/versionsresponds. - The
policyengine-releaseupdater reads onlyclient_payload.version, so it cannot confirm that the wheel it installs carries the bundle the release certified.
This issue covers the identity half of production readiness:
- Carry the certified default dataset SHA-256 from the installed policyengine.py bundle through the executor bundle, the routing state and
PolicyEngineBundle.dataset_sha256. - Expose each deployed wrapper version's bundle identity on
/versions(bundles). - Have the deploy smoke assert the expected identity:
latestroutes to the deployed policyengine version, with its UK model and dataset SHA-256, on the candidate and after promotion. - Have the updater verify the release dispatch's bundle identity against the installed wheel and record the digests in the PR.
A numerical release sentinel and a tested rollback follow in a separate PR.
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.7可能已有人在做 @policyengine 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 55/100
PolicyEngine/policyengine-sim-api#745 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.6可能已有人在做 @policyengine 于 2 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 12/100
PolicyEngine/policyengine-sim-api#738 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.4可能已有人在做 @policyengine 于 3 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 15/100
PolicyEngine/policyengine-sim-api#736 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.3可能已有人在做 @policyengine 于 3 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 15/100
PolicyEngine/policyengine-sim-api#734 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
gradio-app/gradio#13964 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 93/100
BSData/horus-heresy-3rd-edition#3232 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
jbacalso24/mimry#123 ·
维护者通常 1 天内回复
-
p:3-mid pydanty:bug pydanty:is-working
难度 2/5 1-3 小时 新手友好度 76/100
pydantic/pydantic-ai#10153 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue priority: medium size: S testing
难度 2/5 1-3 小时 新手友好度 85/100
cubrid-lab/cubrid-cookbook-python#316 ·
维护者通常 1 天内回复