IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered: I'm using Cloud Build to run gcloud and deploy my Cloud Run job. I was using env in the cloudbuild.yaml to pass the env vars as a list, but that no longer seems to work which breaks my Cloud Run job

What you expected to happen: Env vars should be passed. It used to, but doesn't seem to work anymore. According to the Cloud Build job schema, this should still be accepted/working.

Steps to reproduce: Use Cloud Build to deploy a Cloud Run job and try to pass env vars using env within the step definition, you can confirm the the env vars doesn't get passed.

Other information (workarounds you have tried, documentation consulted, etc): The workaround I have used is to use --set-env-vars option as part of the gcloud run deploy command to pass the env vars instead. It doesn't look as pretty/neat, but it works as the workaround