Synchronize UK private-data and Cloud Run runtime credentials

Fermée
#3,865 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, google-cloud, huggingface, python

Piste de recherche

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.

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

Description

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.
Langage dominant
Python
Étoiles
18
Forks
33
Merge moyen
2 j 3 h
PR mergées (30 j)
72

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

Toutes les issues de PolicyEngine/policyengine-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.