The GitHub Actions job "Scalafmt" on pekko-connectors.git/google-top-level-project-id has succeeded. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: 846f973d6feca806f66f7aa1907370bc1fa48691 / PJ Fanning <[email protected]> Google: add top-level project-id setting with environment fallback The project id was always taken from the credentials provider, so the only way to target a project other than the one owning the credentials' principal was to override GoogleSettings.projectId programmatically. That is a common setup: a service account in one project is frequently granted access to resources in another. Add two top-level settings under pekko.connectors.google: * project-id, which takes precedence over the credentials provider; * default-project-id, used when neither of the above supplies a value, and populated from the GOOGLE_CLOUD_PROJECT, GCLOUD_PROJECT and GCP_PROJECT environment variables that GCP runtimes and GKE Workload Identity set. Both are additive and default to empty, so existing configurations resolve the same project id as before. Configs built without the new keys keep working. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/pekko-connectors/actions/runs/34050126058 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
