Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CloudFunctions2Function support for spec.buildConfig.serviceAccount #3492

Open
3 tasks done
Silvest89 opened this issue Jan 16, 2025 · 0 comments
Open
3 tasks done

CloudFunctions2Function support for spec.buildConfig.serviceAccount #3492

Silvest89 opened this issue Jan 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@Silvest89
Copy link

Checklist

  • I did not find a related open enhancement request.
  • I understand that enhancement requests filed in the GitHub repository are by default low priority.
  • If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

apiVersion: cloudfunctions2.cnrm.cloud.google.com/v1alpha1
kind: CloudFunctions2Function

We usually use custom SA's for all our permission configurations. And would rather not fall back onto the default SA for cloud builds.
It would be nice for the CRD and ConfigConnector to support this field. Terraform Functions2 already supports.

Image

Additional information

No response

Importance

This is both a nice to have and a pain point.
I would like support for this so we can follow best practices and create single-purpose service accounts and thus limit service account privileges

@Silvest89 Silvest89 added the enhancement New feature or request label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant