deploys with 15.17.0 fail without explicit `setGlobalOptions({ region: 'us-central1' })` with vpcConnector

[samsargent]

Looks like our CI is using the latest 15.17.0 somehow and deploys are failing today when they worked fine on the previous release.

It works if including setGlobalOptions({ region: 'us-central1' }) in the index.ts file but this seems like a regression?

[REQUIRED] Environment info

firebase-tools: 15.17.0

Platform: Ubuntu (github CI)

[REQUIRED] Test case

Deploy a function like this:

export const jobCreated = onDocumentCreated(
  {
    document: `jobs/{jobId}`,
    vpcConnector: 'connector-name',
    vpcConnectorEgressSettings: 'PRIVATE_RANGES_ONLY',
  },
  onCreateJob
)

[REQUIRED] Steps to reproduce

Try deploying a function defined like that without setGlobalOptions({ region: 'us-central1' })

These are existing functions already in us-central1 - the same region as the VPC connector.

[REQUIRED] Expected behavior

Function deploys as expected.

[REQUIRED] Actual behavior

Errors with: functions: Request to https://cloudfunctions.googleapis.com/v2/projects/%%service-url%% had HTTP Error: 400, Could not update Cloud Run service servicename. spec.template.metadata.annotations: The target region us-central1 for the deployment must be the same as the reg

[aalej]

Sorry you encountered this issue, and thanks for reporting this to us @samsargent. I was able to reproduce the error. We made some changes related to the Cloud Function's default resource locations and it's possible this caused the issue. Will raise this to our engineering team and mark this as reproducible.

Sharing my mcve here - https://github.com/aalej/issues-10467

[samsargent]

Thanks @aalej - I did see something about that in the changelog when I went digging so figured as much - thanks for making the example repro for me!

Everything is in us-central1 for us do that workaround seems to be working ok for now.