Deploy deploy-cloud-functions ignores service account

[ngreven-allegro]

TL;DR

When trying to use the deploy step in deploy-cloud-functions, it ignores the service_account_email setting.

We've created a new service account (SA) for our project in GCP. We've been trying to deploy it, but no matter what we do it will not deploy using the SA specified. It will always revert to the default SA (called 'Compute Engine default service account' on Google Cloud). The service_account_email seems to be ignored.

Expected behavior

Setting the service_account_email in deploy-cloud-functions should use the specified SA instead of the standard one.

I've tried using v3 of deploy-cloud-functions as well, replacing service_account_email with service_account instead. Unfortunately it gives me the exact same behaviour as described.

Both workload_identity_provider and service_account in the 'auth' step are defined, but I changed them in this bug report for security reasons.

Observed behavior

The default service account is used, service_account_email is ignored.

Action YAML

name: CI

on:
  push:
    branches: [ "master" ]

jobs:
  deploy:
    name: Deploy to GCP
    runs-on: [ self-hosted, ubuntu-latest ]
    container:
      image: artifactory-url/ubuntu:20.04
    permissions:
      contents: 'read'
      id-token: 'write'

    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
          ref: ${{ github.head_ref }}

      - id: 'auth'
        uses: 'google-github-actions/auth@v2'
        with:
          workload_identity_provider: 'xxx'
          service_account: 'yyy'

      - id: 'deploy'
        uses: 'google-github-actions/deploy-cloud-functions@v2'
        with:
          name: 'qqq'
          runtime: go122
          project_id: zzz
          region: europe-central2
          service_account_email: 'fff'

Log output

No response

Additional information

No response

[sethvargo]

Hi there - could you please provide the debug output for the complete GitHub Actions workflow run for v3?