Status Update
Comments
pu...@google.com <pu...@google.com>
pu...@google.com <pu...@google.com>
ch...@google.com <ch...@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
qi...@google.com <qi...@google.com> #3
An customer is blocked by the bug:
is there any timeline for the fix, thanks.
Description
Problem you have encountered:
When configuring VPC-SC for BigQuery the necessary permission create TensorFlow models was not supported.
bigquery.models.updateData
togoogleapi: Error 400: Invalid Directional Policies set in Perimeter 'accessPolicies/<access_policy>/servicePerimeters/<project_id>': Error in IngressTo: PERMISSION 'bigquery.models.updateData' is not supported in bigquery.googleapis.com
What you expected to happen:
The model permissions , e.g.
bigquery.models.updateData
permission should be added to the other supportedbigquery.models.getData
andbigquery.models.updateMetadata
are already supported.Steps to reproduce:
bigquery.models.updateData
permission as selected method for BigQuery APIERROR: (gcloud.access-context-manager.perimeters.create) INVALID_ARGUMENT: Invalid Directional Policies set in Perimeter 'accessPolicies/67977849759/servicePerimeters/bug': Error in IngressTo: PERMISSION 'bigquery.models.updateData' is not supported in bigquery.googleapis.com
Other information (workarounds you have tried, documentation consulted, etc):
Allowing all methods and permissions seems to be a workaround, though not desirable in our use-case.