Assigned
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Hello,
Thanks for reaching out to us!
The Product Engineering Team has been made aware of your feature request, and will address it in due course. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new [Issue Tracker]
Thanks and Regards,
Onkar Mhetre
Google Cloud Support
al...@shopify.com <al...@shopify.com> #3
Comment has been deleted.
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com>
er...@pactum.com <er...@pactum.com> #4
Note: for Cloud Functions and Cloud run there is at least possibility to define some permissions at resource level, but it seems impossible to grant any IAM principal ability to execute only single Cloud Scheduler Job in given project, violating principle of least privileges.
st...@google.com <st...@google.com> #5
I believe IAM Conditions are supported by the Cloud Run API (I'll see to confirm that soon)
Description
Issue summary: Customer has deployed a function to make some queries on our Cloud SQL instances databases. Note, the Cloud SQL instances use the private IP address connectivity only. They have setup a Serverless VPC Access connector to be able to connect from the Cloud Functions to our Cloud SQL instances privately and it works well.
They would like to let the developers being able to create new Cloud Functions which leverage the private connectivity into their host project. But, they would like to restrict their IAM roles on some others existing function based on their names or labels.