Enable CI/CD integration testing with Secret Manager#131
Enable CI/CD integration testing with Secret Manager#131google-labs-jules[bot] wants to merge 1 commit into
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
pkg/secrets: Now prioritizes environment variables over Secret Manager. This allows local overrides and simplifies testing, while still falling back to Secret Manager in CI if env vars are missing butGCLOUD_PROJECT_IDis present.deployment.yml: Authenticate withgcloudbefore the "Install, Build, Test" step. PassedGCLOUD_PROJECT_IDto the test environment.api_client_test.go,passage_test.go, andask_test.go. "Success" scenarios now rely on the environment (or Secret Manager) to provide the API URL, effectively converting them to integration tests when running in CI. "Error" scenarios continue to use mocks.pkg/app/database_integration_test.goto verify connectivity toUSER_DATABASE_ID(Firestore) using a safe dummy user.PR created automatically by Jules for task 535107038277093355 started by @julwrites