From 7e8b5e264d044d6b993c530290e5bba1d10f52cc Mon Sep 17 00:00:00 2001 From: Nick Youngblut Date: Wed, 10 Apr 2024 04:10:02 -0700 Subject: [PATCH] Updated docs on Google Cloud setup and credentials (#4896) [ci skip] --- docs/config.md | 3 +++ docs/google.md | 3 +++ 2 files changed, 6 insertions(+) diff --git a/docs/config.md b/docs/config.md index 123d032f8e..a3cd1e34db 100644 --- a/docs/config.md +++ b/docs/config.md @@ -857,6 +857,9 @@ The following settings are available for Google Cloud Batch: `google.batch.serviceAccountEmail` : Define the Google service account email to use for the pipeline execution. If not specified, the default Compute Engine service account for the project will be used. + Note that the `google.batch.serviceAccountEmail` service account will only be used for spawned jobs, not for the Nextflow process itself. + See the [Google Cloud](https://www.nextflow.io/docs/latest/google.html#credentials) documentation for more information on credentials. + `google.batch.spot` : When `true` enables the usage of *spot* virtual machines or `false` otherwise (default: `false`). diff --git a/docs/google.md b/docs/google.md index 0fc51b0ab9..69ee86f83f 100644 --- a/docs/google.md +++ b/docs/google.md @@ -35,6 +35,9 @@ Then, define the following variable replacing the path in the example with the o export GOOGLE_APPLICATION_CREDENTIALS="/path/your/file/creds.json" ``` +See [Get started with Nextflow on Google Cloud Batch](https://www.nextflow.io/blog/2023/nextflow-with-gbatch.html) for more information on how to use Google Cloud Batch, +including how to set the required roles for your service account. + (google-batch)= ## Cloud Batch