Synchronize UK private-data and Cloud Run runtime credentials

Geschlossen
  • Stimmt etwas nicht?
#3,865 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, google-cloud, huggingface, python
Bereich
cloud, databases, devops, security

Rechercherichtung

Start with the deployment workflows and the manually dispatched synchronization workflow entry point, then trace the existing Secret Manager and Cloud Run credential handling. Add coverage for idempotency, environment separation, value verification, and IAM checks without exposing secrets. Done means deployments bind the specified Hugging Face resource, documentation describes ownership and synchronization, and staging retains its distinct database password.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Problem

Cloud Run deployments need an unambiguous, read-only Hugging Face credential for the private UK datasets. GitHub-owned runtime credentials also need to be copied to Google Secret Manager and have their Cloud Run access bindings verified before deployment.

Required behavior

  • Use PE_UK_PRIVATE_HF_READ_TOKEN as the GitHub secret and pe-uk-private-hf-read-token as the Google Secret Manager resource.
  • Verify that the Hugging Face credential is read-only and can access both required private UK repositories.
  • Synchronize shared GitHub-owned runtime secrets before staging and production deployments.
  • Synchronize the production database password only for production; preserve the distinct GCP-managed staging database password.
  • Avoid creating redundant Secret Manager versions when values have not changed.
  • Verify stored values and Cloud Run service-account permissions without printing secret values.
  • Provide a manually dispatched synchronization workflow for credential rotation and recovery.

Acceptance criteria

  • Deployment and manual workflows synchronize the correct environment-specific secret set.
  • Tests cover idempotency, environment separation, value verification, and IAM verification.
  • Deployment validation confirms the expected Hugging Face Secret Manager binding.
  • Documentation states the credential ownership and synchronization path.
Vorherrschende Sprache
Python
Sterne
18
Forks
33
Ø Merge
2 T. 9 Std.
Gemergte PRs (30 T.)
77

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-api

Alle Issues in PolicyEngine/policyengine-api

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

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