Assigned
Status Update
Comments
ar...@google.com <ar...@google.com> #2
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible, please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered: Existing limitation is when you try to create a push subscription with push endpoint as cloud function in a project which is protected by VPC service control perimeter. When we try to create the push subscription using terraform where push endpoint is a cloud function, we are noticing "Request is prohibited by organization's policy" error.
What you expected to happen: We want to have Cloud function as Push endpoint. Existing limitation is when you try to create a push subscription with push endpoint as cloud function in a project which is protected by VPC service control perimeter. When Cloud function and pub/sub are within the vpc-sc perimeter we should be able to use this CF as push endpoint in pub sub.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc.):