Status Update
Comments
da...@google.com <da...@google.com>
ba...@google.com <ba...@google.com>
ma...@google.com <ma...@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.
Thanks & Regards,
Ashalatha
Google Cloud Support
vl...@google.com <vl...@google.com> #3
Are there any updates regarding this matter at hand?
br...@dgfip.finances.gouv.fr <br...@dgfip.finances.gouv.fr> #4
Hello, Waiting for news about a case on the support side. Thanks for your time, regards, Brice
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com> #5
Hello Team,
We got an update from the product team stating that, "There is a current issue with Dataflow where such VPC Service Controls violations are logged. The team is working on fixing the issue such that the violations don't appear in the logs. Note that Dataflow functionality is not impacted by these violations, the only side effects are the recorded violations." Further updates regarding this issue will be communicated here in this thread.
Thanks & Regards,
Manish Bavireddy.
Google Cloud Support
Description
NO_MATCHING_ACCESS_LEVEL VPC SC ingress violation and the principal email is "google-internal” which cannot be set in the VPC service perimeter since it is not a valid Identity .
What you expected to happen:
See the exact principal email in the error message to be able to set an ingress rule.
Other information (workarounds you have tried, documentation consulted, etc):