env config not working with GCP Batch

[nick-youngblut]

Bug report

My nextflow.config contains:

env {
    MY_ENV_VAR = "my_value"
}

When the executor is local, the process using MY_ENV_VAR via os.environ["MY_ENV_VAR"] runs successfully.
However, when the executor is google-batch, the process throws KeyError: 'MY_ENV_VAR'.

https://www.nextflow.io/docs/latest/reference/config.html#env does not state that env is not supported for google-batch, so I'm assuming that there is either a bug or a lack of docs.

Expected behavior and actual behavior

Environmental variables set via the env config scope should be available for GCP Batch jobs... or the docs should explicitly state that env is not supported for GCP Batch.

Steps to reproduce the problem

• Set variables in the env scope
• Run locally; processes using the env variable should succeed
• Run on GCP Batch; processes using the env variable should fail

Environment

• Nextflow version: 24.10.2
• Java version: 21.0.0
• Operating system: Ubuntu 22.04.5
• Bash version: 5.1.16

[pditommaso]

I'm unable to replicate this. Can you please provide a test case ?