You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with version 469.0.0 of google-cloud-cli, executing the bq command results in the following error:
bq --project_id test --api http://localhost:9051 ls
BigQuery error in ls operation: Got 500 response from discovery url: http://host.docker.internal:9051/$discovery/rest?version=v2
I tested the difference between versions using the docker image of google-cloud-cli. It works fine up until version 468.0.0, but does not work from version 469.0.0.
❯ docker run gcr.io/google.com/cloudsdktool/google-cloud-cli:468.0.0 bq --project_id test --api http://host.docker.internal:9051 ls
datasetId
-------------------------------------------
test1
test
bqjob_r4a554d13245e76d_0000018eac057299_1
❯ docker run gcr.io/google.com/cloudsdktool/google-cloud-cli:469.0.0 bq --project_id test --api http://host.docker.internal:9051 ls
BigQuery error in ls operation: Got 500 response from discovery url: http://host.docker.internal:9051/$discovery/rest?version=v2
(I use Docker Desktop on Mac and run emulator on the host machine, so endpoint is host.docker.internal. Some options are omitted)
The error occurs not just with the bq ls command, but with other commands like query as well.
What happened?
Starting with version 469.0.0 of google-cloud-cli, executing the bq command results in the following error:
I tested the difference between versions using the docker image of google-cloud-cli. It works fine up until version 468.0.0, but does not work from version 469.0.0.
(I use Docker Desktop on Mac and run emulator on the host machine, so endpoint is host.docker.internal. Some options are omitted)
The error occurs not just with the bq ls command, but with other commands like query as well.
Server version is current HEAD: 3f8779e
What did you expect to happen?
I expected it to work correctly and return a response, just like it did when executed with version 468.0.0.
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
workaround
As a workaround, you can:
cause
Discovery API Endpoint has been changed.
We need to create a new handler to handle the new API
The text was updated successfully, but these errors were encountered: