Give the Simulation Entrypoint its own simulation schema, migration chain and database connection
维护者通常 1 天内回复
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
调研方向
Start by reading the Simulation Entrypoint deployment and readiness checks, the repository's migration ownership rules, and existing Alembic and PostgreSQL CI configuration. The issue names migrations/ as the chain location and SIMULATION_DATABASE_URL as the runtime setting; first confirm the staging and production roles, URLs, and grants have been created. Done means the entrypoint deploys with an empty simulation schema at its first revision, readiness reports that revision, the candidate check matches it to the image, and CI completes the upgrade, check, downgrade, and upgrade cycle.
由索引模型根据 Issue 内容生成。
描述
The Simulation Entrypoint will record simulations, reports, their runs and their results in its own Postgres schema, simulation, in the database that holds the Public API's v2 tables. Before any table can be added, the service needs the foundation:
- a persistence library for that schema, with its own Alembic migration chain;
- a migration job that applies the chain before each entrypoint deploy, using a separate migrator role;
- the runtime role's database URL (
SIMULATION_DATABASE_URL) mounted on the entrypoint as a pinned Secret Manager version; - the schema's applied revision reported by the readiness check, and required by the candidate check to match the image;
- ownership rules in place of the rule that forbade any migration chain in this repository: one chain at
migrations/, its version table in thesimulationschema, the Modal executor and gateway independent of the library, and no database URL in Modal except the Stage 12 comparison path's own; - a CI job that runs the chain's upgrade, check, downgrade and upgrade cycle on PostgreSQL.
Once deployed, the entrypoint has a database connection and an empty simulation schema at its first revision; nothing reads or writes it yet. The database roles, URLs and grants must be created by an operator in staging and production first.
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 17 小时
- 30 天内合并 PR
- 60
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Update policyengine to 6.7.3可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 半天 新手友好度 70/100
PolicyEngine/policyengine-sim-api#823 ·
维护者通常 1 天内回复
-
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.10.2可能已有人在做 @policyengine 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 25/100
PolicyEngine/policyengine-sim-api#908 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-sim-api#907 ·
维护者通常 1 天内回复
-
Update policyengine to 6.10.1可能已有人在做 @policyengine 于 1 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 20/100
PolicyEngine/policyengine-sim-api#905 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
iceboundrock/AutoForge#304 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
fossasia/visdom-dev#77 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
aws-cloudformation/cfn-lint#4890 ·
维护者通常 2 天内回复