onRequest doesn't support setting `Execution Environment`

[tony-g]

Related issues

Not that I could find searching for execution environment or deployment args - sorry if I missed something!

[REQUIRED] Version info

node:
v22.17.0

firebase-functions:
6.6.0
firebase-tools:
14.20.0

firebase-admin:
13.5.0

[REQUIRED] Test case

Cloud Run Functions has this Execution Environment setting

https://cloud.google.com/run/docs/about-execution-environments

It's of course possible to update post-deploy, but it would be cleaner if we could co-locate these settings.

[REQUIRED] Steps to reproduce

N/A (Feature request, not a bug)

[REQUIRED] Expected behavior

Would be great if there was a setting (so we can keep all the settings together)

onRequest({ executionEnvironment: 'gen2', otherSettings }, theFunction)

I could imagine it's not appealing to maintain options for every Cloud Functions setting - Not sure if this is practical either, but since this appears to be a supported argument during function deploy, maybe there could be an escape hatch to allow us to specify deploy args?

onRequest({ deployArgs: { 'executionEnvironment': 'gen2' } }, theFunction)
// which would get translated into the equivalent of the `--execution-environment gen2`

[REQUIRED] Actual behavior

N/A

Were you able to successfully deploy your functions?

N/A

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[CorieW]

Hey @tony-g,

You can access 1st gen stuff by importing firebase-functions/v1.

1st gen: https://firebase.google.com/docs/reference/functions/firebase-functions
2nd gen: https://firebase.google.com/docs/reference/functions/2nd-gen/node/firebase-functions

[tony-g]

Thanks @CorieW - Uh sorry, I think I was confused and asked the wrong thing :)

• I have a function that's running about 25% faster in the gen2 execution environment (so I want gen2, not gen1)
• I'm importing from v2 like this

const { onRequest } = require('firebase-functions/v2/https')

• When I deploy the function, it's showing up as Default in Cloud Run console.

• Cloud Run appears to be choosing 'wrong' for me for this particular function, as I get the better performance when I manually set it to gen2.
• So ideally, we'd be able to lock this to gen2 along with the other settings. (We can set it manually via the console or gcloud, but in an ideal world would be preferable if it we were able to specify it along with other settings (cpu, memory, etc.))