Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#897 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@anth-volk y travaille déjà.

Depuis le 22/10/2026.

  • #898 par @anth-volk — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
postgresql, python, sqlalchemy
Domaine
backend, databases, devops

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
1
Forks
1
Merge moyen
1 j 16 h
PR mergées (30 j)
61

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de PolicyEngine/policyengine-sim-api

Toutes les issues de PolicyEngine/policyengine-sim-api

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.