Status Update
No update yet.
Comments
dh...@google.com
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.
Thanks & Regards,
Ashalatha
Google Cloud Support
Description
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:
Encountered an issue where a VPC SC Ingress rule where the source parameter is not a project or a VPC network, but instead is able to accept a folder as an argument would be convenient.
This would allow policies to be more concise by not having to enumerate all of the projects within a folder for example which would make the VPC SC policies less brittle as more projects get added.
I see based on [1] that currently only a VPC network or a project can be added here.
[1]
What you expected to happen:
That the syntax for Ingress rules would be able to add a folder id for the source parameter.
Steps to reproduce:
N/A
Other information (workarounds you have tried, documentation consulted, etc):