ci: pass all env vars & secrets to Google Cloud Run and Firebase Studio#353
Open
Copilot wants to merge 3 commits into
Open
ci: pass all env vars & secrets to Google Cloud Run and Firebase Studio#353Copilot wants to merge 3 commits into
Copilot wants to merge 3 commits into
Conversation
Copilot
AI
changed the title
Pass all env vars and secrets to Google Cloud Run and Firebase Studio
ci: pass all env vars & secrets to Google Cloud Run and Firebase Studio
May 30, 2026
Copilot created this pull request from a session on behalf of
LVT-ENG
May 30, 2026 00:39
View session
Member
There was a problem hiding this comment.
Pull request overview
Introduces a first-pass Google Cloud Run deployment pipeline for the Python API, plus a Firebase Studio (IDX) dev workspace definition and a helper script to seed Google Secret Manager from local env/.env files—centralizing environment variable/secret configuration for deployment and development.
Changes:
- Added a
Dockerfileto containerize the Flask API for Cloud Run using Gunicorn. - Added a GitHub Actions workflow to build/push to Artifact Registry and deploy to Cloud Run with env vars + Secret Manager bindings.
- Added Firebase Studio workspace config (
.idx/dev.nix) and a secret-seeding helper script (scripts/setup_google_secrets.py).
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
scripts/setup_google_secrets.py |
Adds a CLI utility to create/update Secret Manager secrets from env / .env.local. |
Dockerfile |
Defines the Cloud Run container image for the Python API (Gunicorn entrypoint). |
.idx/dev.nix |
Adds Firebase Studio workspace packages, env var stubs, and startup/preview commands. |
.github/workflows/deploy-cloud-run.yml |
Adds CI/CD workflow to deploy the API to Cloud Run and inject configuration via env/secrets. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No CI/CD existed for Google Cloud deployment, and no development workspace config was defined for Firebase Studio. All 35+ env vars/secrets were scattered across the codebase with no single source of truth for deployment.
Changes
Dockerfile— Containerizes the Flask API (api/) with Python 3.12-slim + Gunicorn; entry point for Cloud Run.github/workflows/deploy-cloud-run.yml— Builds image → Artifact Registry → deploys to Cloud Run onmainpush; sensitive vars injected via Google Secret Manager (secrets:), non-sensitive viaenv_vars:.idx/dev.nix— Firebase Studio workspace declaring all env-var stubs, required packages (python312,nodejs_20,corepack), andonStartcommands for API + frontendscripts/setup_google_secrets.py— One-time helper to seed Google Secret Manager from a local.env.local; secret values are encoded to bytes before upload and never appear in any log outputSecrets coverage
STRIPE_ENDPOINT_SECRET,GEMINI_API_KEY,GMAIL_*,GOOGLE_SERVICE_ACCOUNT_JSON,PENNYLANE_API_KEY,LINEAR_API_TOKEN,GOOGLE_SHEETS_*,PAU_TTS_*, and morevars.*)LAFAYETTE_VERIFY_BASE_URL,JULES_MAIL_MAX_RESULTS,LINEAR_PAGE_SIZE,GOOGLE_SHEETS_RANGE, etc.VITE_OAUTH_PORTAL_URL,VITE_APP_ID,VITE_FRONTEND_FORGE_API_KEY,VITE_ANALYTICS_*Required one-time setup
python scripts/setup_google_secrets.py --dry-run→ then run without--dry-runto populate Secret ManagerGCP_PROJECT_IDas a GitHub Actions variable; addGCP_SA_KEY(service account JSON with Cloud Run + Secret Manager roles) as a secrettryonyouineurope-west1