Looker Query ID API Patch Notice

[SivanarayanaReddyTamalampudi]

Hi Team,

We are using gazer commands to migrate the GUI content from one environment to another environment, as part of recent announcement reg the API end point change (below)which is going push to all the instances from looker on 22nd feb 2024.

• GET /queries/<query_id>
• POST /render_tasks/queries/<query_id>/<result_format>
• GET /running_queries
  when we enable the "Disallow Numeric Query IDs" in Admin ⇾ Legacy we are getting the error like
  GET [https://xxxxxxxxx.cloud.looker.com/api/4.0/queries/1833226] 404 - The resource you're looking for could not be found :for the script : gzr folder export xxxxx--host=xxxxxx.cloud.looker.com --port=443 --client-id=xxxxxx --client-secret=xxxxxxx , do you have any solution for this issue. when we disable "Disallow Numeric Query IDs" didn't see any issue.

[SivanarayanaReddyTamalampudi]

from the doc we found this, not sure how come it will convert from query_id to slug , as we are using like this commands
gzr folder export xxxxx--host=xxxxxx.cloud.looker.com --port=443 --client-id=xxxxxx --client-secret=xxxxxxx
The GET /queries/<query_id> endpoint requires a slug for the query_id. A query_id that is given a numeric query ID will return a 404 error.
The POST /render_tasks/queries/<query_id>/<result_format> endpoint requires a slug for the query_id. A query_id that is given a numeric query ID will return a 404 error.
The GET /running_queries endpoint is restricted to Looker admins only.

[nicoledavistmx]

We are having this issue as well. Thursday the 22nd we are being upgraded which will Disallow Numeric Query IDs, so I'm concerned our pipeline will break. Has anyone found a workaround?

[SivanarayanaReddyTamalampudi]

Team,
Any update from gazer regarding the below command which throws 404 error due to new change from looker.
script:
gzr folder export xxxxx--host=xxxxxx.cloud.looker.com --port=443 --client-id=xxxxxx --client-secret=xxxxxxx

Error:
GET https://xxxx.cloud.looker.com/api/4.0/queries/1833226:

404 - The resource you're looking for could not be found

[drstrangelooker]

I'm looking at it right now.

[drstrangelooker]

I just released version 0.3.13.

Please update and give me feedback that it is working for you.

[drstrangelooker]

If you aren't familiar the update command is

gem update gazer

[SivanarayanaReddyTamalampudi]

Thanks for the fix, now existing gazer script are working as expected like before after enabling the "
Disallow Numeric Query IDs (Recommended by Google Cloud)" option as well.

[nicoledavistmx]

Same, we were able to push code just now without issue where we had problems previously. Thanks @drstrangelooker!