Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Give the Simulation Entrypoint its own simulation schema, migration chain and database connection

Aperta
  • Qualcosa non va?
#897 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@anth-volk ci sta già lavorando.

Dal 22/10/2026.

  • #898 di @anth-volk — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
postgresql, python, sqlalchemy
Ambito
backend, databases, devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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 the simulation schema, 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.

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
1g 17h
PR unite (30g)
60

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PolicyEngine/policyengine-sim-api

Tutte le issue di PolicyEngine/policyengine-sim-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.