Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 82937]
Primary programming language affected, if applicable [ID: 82936]
[ID: 82935]
[ID: 82940]
[ID: 82941]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
*Problem you have encountered*:
We have many Gen1 Cloud Functions deployed/managed using Terraform, recently as a security policy we decided to use a custom service account for running the cloud function build in cloud builds. When we tried to explore for options we came across this Gen2 Cloud Function page:
And relevant configuration in Terraform:
However, we couldn't able to find anything related to this in Gen1 Cloud Function configuration.
*What you expected to happen*:
Please add this feature to Gen1 cloud function too or suggest us an alternate approach where we can deploy a Gen1 cloud function and it uses custom service account for cloud build. If you are providing an alternative approach, Please elaborate on the permissions too.