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

Add the Simulation Entrypoint's own Postgres schema, persistence library and migration chain

Fermée
  • Quelque chose ne va pas ?
#844 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

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

Personne n'a encore pris cette issue.

  • #847 par @anth-volk — fermée sans fusion

É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
github-actions, google-cloud, postgresql, python
Domaine
backend, databases, devops

Piste de recherche

Start by reading the repository rule sim.stage12.no-migration-chain and the existing migration and deploy workflows. The issue names libs/policyengine-simulation-persistence, migrations/, and GET /ready as the main entry points; map their existing conventions before changing them. Done means the migration chain passes upgrade, check, downgrade, and upgrade on fresh PostgreSQL, deploy applies it before the candidate, and the existing pass-through routes and Stage 12 comparison still behave as before.

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

Description

Context

Step 1 of the API v2 migration (item 1A-2) gives the Simulation Entrypoint its own durable state in the v2 Postgres database. Today the repository rule sim.stage12.no-migration-chain forbids any Alembic chain here: the only tables the simulation services touch are the temporary Stage 12 comparison tables, which the Public API owns and migrates.

Scope

  • Replace sim.stage12.no-migration-chain with ownership rules for the Simulation Entrypoint's own schema:
    • one Alembic chain at migrations/, schema simulation, version table simulation.alembic_version;
    • the Modal executor and gateway never depend on the persistence library;
    • no Modal secret or deployment receives a simulation database URL (the Stage 12 secret stays the only database credential in Modal until Stage 12 is removed).
  • Add libs/policyengine-simulation-persistence with an initial revision, and a CI job that runs the chain's upgrade, alembic check, downgrade and upgrade on a fresh PostgreSQL.
  • Add a deploy job that applies the migrations before the Simulation Entrypoint candidate deploys, using a migrator URL that only that job receives.
  • Give the Simulation Entrypoint SIMULATION_DATABASE_URL (runtime role) from Secret Manager, and report the database's migration revision in GET /ready.

The old-gateway pass-through routes and the Stage 12 comparison must behave exactly as before; nothing in production reads or writes the new schema yet.

Operator prerequisites (both environments, before merge)

Merging to main deploys staging and then production, and the deploy requires these:

  • Create the simulation_migrator and simulation_runtime database roles in the staging and production v2 databases. simulation_migrator must be able to create the simulation schema (or the schema must be created in advance and owned by it).
  • Store the migrator URL as the SIMULATION_MIGRATION_DATABASE_URL secret in this repository's beta and prod GitHub environments.
  • Store the runtime URL in Secret Manager in the Simulation Entrypoint's Google Cloud project, readable only by sim-entry-beta-runtime and sim-entry-prod-runtime (and listable by the deploy service account), and set its name as the SIMULATION_DATABASE_URL_SECRET_NAME variable in beta and prod.
Langage dominant
Python
Étoiles
1
Forks
1
Merge moyen
1 j 16 h
PR mergées (30 j)
60

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.