Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#897 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@anth-volk arbeitet bereits daran.

Seit 22.10.2026.

  • #898 von @anth-volk — offen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
postgresql, python, sqlalchemy
Bereich
backend, databases, devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
1
Forks
1
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
61

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PolicyEngine/policyengine-sim-api

Alle Issues in PolicyEngine/policyengine-sim-api

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.