Problem listing collections

[bskemp01]

Hey all,

im trying to test the program and trying to list my collections in our tenant, however i am getting the following error:

any help to move forward from this would be appreciated :)

[mountaindude]

Well, that's a rather non-descriptive error message.... could certainly be improved.

Let me test things here to make sure Qlik hasn't recently changed something in QS Cloud.
I do test Butler Sheet Icons regularly to ensure it works against current QS Cloud version, it's been a couple of months since last check now though.
Date for last check is found here, btw.

[mountaindude]

Listing collections works for me:

My tenant is in EU rather than US. No idea whether QS Cloud differ behind the scenes between EU and US...

In theory two different tenants could be served different code by Qlik.
For example, when new versions of QS Cloud are rolled out that is probably done over several days (or longer?).
No way to test that/verify that hypothesis though.

Maybe some of your parameters to BSI are incorrect?

In the example above that worked for me the variables had the following values:

BSI_CLOUD_TENANT_URL=hni......eu.qlikcloud.com
BSI_CLOUD_API_KEY=eyJhbGciOi.....

I do get the same error as you when I provide an incorrect or invalid API KEY.
So that could be worth looking into for you.

Meanwhile I'll put on the todo list to improve logging a bit in next version of the tool.

[bskemp01]

Good day, Thank you for replying so quickly ☺️ I will check the API key but this error was appearing for my colleague as well. I will get back after I tested the key.

…

On Fri, Feb 9, 2024, 9:15 AM Göran Sander ***@***.***> wrote: Listing collections works for me: image.png (view on web) <https://github.com/ptarmiganlabs/butler-sheet-icons/assets/1029262/0b210653-6f5d-4a35-8cf1-b4579b2702ac> My tenant is in EU rather than US. No idea whether QS Cloud differ behind the scenes between EU and US... In theory two different tenants could be served different code by Qlik. For example, when new versions of QS Cloud are rolled out that is probably done over several days (or longer?). No way to test that/verify that hypothesis though. Maybe some of your parameters to BSI are incorrect? In the example above that worked for me the variables had the following values: BSI_CLOUD_TENANT_URL=hni......eu.qlikcloud.com BSI_CLOUD_API_KEY=eyJhbGciOi..... I do get the same error as you when I provide an incorrect or invalid API KEY. So that could be worth looking into for you. Meanwhile I'll put on the todo list to improve logging a bit in next version of the tool. — Reply to this email directly, view it on GitHub <#468 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWF6GUGSML76PEVOL4NDVB3YSY4QDAVCNFSM6AAAAABDBRNIFCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRQGE4TC> . You are receiving this because you authored the thread.Message ID: <ptarmiganlabs/butler-sheet-icons/repo-discussions/468/comments/8420191@ github.com>

[bskemp01]

ok looks like its not the api key

i will keep trying some things

[mountaindude]

Hmm... Not sure what's going on there.

Could it be related to permissions for the user in question?
These things have changed over past months in QS Cloud, maybe it's related.

Here are settings for my user:

[bskemp01]

I am not the tenant owner but i am one of two developers here. i have all permissions you have except the steward.

[bskemp01]

i tried a different command the create-sheet-thumbnails and i see a little more info if this helps.

[mountaindude]

Same thing there, those [object Object] log messages aren't really helpful.

I am in the process of releasing a new BSI version with better/more helpful logging, should be out within the hour.
That will hopefully tell us more what's causing the problem.

You can also try adding --loglevel verbose or even --loglevel debug when running the tool.
That will increase the logging and it may also give clues to what the root cause of the problem is.

[mountaindude]

@bskemp01, a new BSI version (3.2.2) has just been released, available here.

It's literally just minutes old so I have not tested it myself on Windows, but all the automated tests (incl the ones done on Windows) passed, so it should be fine.

That version includes better logging.
Give it a spin and report back what you see, would be nice sorting out what's causing the issue you're seeing.

[bskemp01]

will do thank you!

[bskemp01]

ok well it does have a bit more information now. here is the screenshot along with the script i am using:

[mountaindude]

Ok, this gives us something to work with.

Looks like a call to QS Cloud fails and the result returned is not what's expected by BSI.
I'll see if I can reproduce the error based on this.

[bskemp01]

Great thanks! And take your time. I will not be back at work until Monday 😊

…

On Fri, Feb 9, 2024, 4:15 PM Göran Sander ***@***.***> wrote: Ok, this gives us something to work with. Looks like a call to QS Cloud fails and the result returned is not what's expected by BSI. I'll see if I can reproduce the error based on this. — Reply to this email directly, view it on GitHub <#468 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWF6GUEVF3GSOUZTDGQM2ODYS2NYNAVCNFSM6AAAAABDBRNIFCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRTG44DQ> . You are receiving this because you were mentioned.Message ID: <ptarmiganlabs/butler-sheet-icons/repo-discussions/468/comments/8423788@ github.com>

[mountaindude]

Think I may have found it.

You don't by any chance have "https://" at the beginning of the --tenanturl parameter?
When I have that I get the same error you get.

If that's the root cause it should prob be classified as a bug...
Formally a URL consists of a protocol (https) and a hostname (tenantid.eu.qlikcloud.com).
But Butler Sheet Icons expects only the hostname, i.e. that parameter is rather badly named.

Changing the name of the parameter would be a breaking change, I think a better option is to
update BSI itself to gracefully accept either a full URL or a hostname, and then fix things so a proper call to QS Cloud can be made.

See bug #476.

[bskemp01]

Since this GitHub is my personal account I'm getting emails so I respond 😊 but no actually I did not have that. I have: Tenant.us.qlikcloud.com But that is an interesting bug.

…

On Fri, Feb 9, 2024, 5:21 PM Göran Sander ***@***.***> wrote: Think I may have found it. You don't by any chance have "https://" at the beginning of the --tenanturl parameter? When I have that I get the same error you get. If that's the root cause it should prob be classified as a bug... Formally a URL consists of a protocol (https) and a hostname ( tenantid.eu.qlikcloud.com). But Butler Sheet Icons expects only the hostname, i.e. that parameter is rather badly named. Changing the name of the parameter would be a breaking change, I think a better option is to update BSI itself to gracefully accept either a full URL or a hostname, and then fix things so a proper call to QS Cloud can be made. See bug #476 <#476>. — Reply to this email directly, view it on GitHub <#468 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWF6GUDFFBUVQGKRQLAUNSLYS2VP7AVCNFSM6AAAAABDBRNIFCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRUGEZDK> . You are receiving this because you were mentioned.Message ID: <ptarmiganlabs/butler-sheet-icons/repo-discussions/468/comments/8424125@ github.com>

[mountaindude]

Hmm. I was so sure. Oh well, putting the thinking 🧢 back on then.

…

On Sat, 10 Feb 2024, 02:23 Brian Kemp, ***@***.***> wrote: Since this GitHub is my personal account I'm getting emails so I respond 😊 but no actually I did not have that. I have: Tenant.us.qlikcloud.com But that is an interesting bug. On Fri, Feb 9, 2024, 5:21 PM Göran Sander ***@***.***> wrote: > Think I may have found it. > > You don't by any chance have "https://" at the beginning of the > --tenanturl parameter? > When I have that I get the same error you get. > > If that's the root cause it should prob be classified as a bug... > Formally a URL consists of a protocol (https) and a hostname ( > tenantid.eu.qlikcloud.com). > But Butler Sheet Icons expects only the hostname, i.e. that parameter is > rather badly named. > > Changing the name of the parameter would be a breaking change, I think a > better option is to > update BSI itself to gracefully accept either a full URL or a hostname, > and then fix things so a proper call to QS Cloud can be made. > > See bug #476 > <#476>. > > — > Reply to this email directly, view it on GitHub > < #468 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AWF6GUDFFBUVQGKRQLAUNSLYS2VP7AVCNFSM6AAAAABDBRNIFCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRUGEZDK> > . > You are receiving this because you were mentioned.Message ID: > <ptarmiganlabs/butler-sheet-icons/repo-discussions/468/comments/8424125@ > github.com> > — Reply to this email directly, view it on GitHub <#468 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH3JDXI3YAKTQNFFNJD4STYS3D2LAVCNFSM6AAAAABDBRNIFCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRUG42TM> . You are receiving this because you commented.Message ID: <ptarmiganlabs/butler-sheet-icons/repo-discussions/468/comments/8424756@ github.com>

[bskemp01]

small update if it helps. i tried to use the node.js version and heres the error from that. not sure if its more info or not

[mountaindude]

@bskemp01

Version 3.3.0 was released earlier today.
It adds both better/more relevant error logging, as well as a connection test to QS Cloud on startup.

All in all the new version should be better at telling what's causing the problems you ran into.

For example, if I list which QS Cloud collections are available to the user associated with the API key, it looks like this (in this case on macOS/Linux):

➜  butler-sheet-icons ./butler-sheet-icons qscloud list-collections --tenanturl $BSI_CLOUD_TENANT_URL --apikey $BSI_CLOUD_API_KEY --outputformat table
2024-02-16T15:27:01.951Z info: App version: 3.2.3
2024-02-16T15:27:01.952Z info: Testing connection to Qlik Sense Cloud...
2024-02-16T15:27:02.841Z info: Connection to tenant hnik......eu.qlikcloud.com successful.
2024-02-16T15:27:02.841Z info:     Tenant ID : cr0KDX....
2024-02-16T15:27:02.841Z info:     User name : Göran Sander
2024-02-16T15:27:02.842Z info:     User email: goran@....
2024-02-16T15:27:02.842Z info:     User ID   : 6337.....
2024-02-16T15:27:03.117Z info: Collections:
╔════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                                                   Butler Sheet Icons                                                                   ║
║                                            Available collections in tenant hni.............eu.qlikcloud.com                                            ║
╟───────────────────────┬────────────────────────────────┬──────────────────────────┬─────────┬────────────┬──────────────────────┬──────────────────────╢
║ Name                  │ Description                    │ ID                       │ Type    │ Item count │ Created at           │ Updated at           ║
╟───────────────────────┼────────────────────────────────┼──────────────────────────┼─────────┼────────────┼──────────────────────┼──────────────────────╢
║ Sheet thumbnails demo │                                │ 65cb8b.................. │ private │ 1          │ 2024-02-13T15:33:08Z │ 2024-02-13T15:36:28Z ║
╚═══════════════════════╧════════════════════════════════╧══════════════════════════╧═════════╧════════════╧══════════════════════╧══════════════════════╝

➜  butler-sheet-icons

Now, if I run the same command with an invalid or expired API token, I will with the latest version of Buter Sheet Icons get more informative errors compared to earlier versions:

➜  butler-sheet-icons ./butler-sheet-icons qscloud list-collections --tenanturl $BSI_CLOUD_TENANT_URL --apikey an-invalid-key --outputformat table
2024-02-16T15:30:54.510Z info: App version: 3.2.3
2024-02-16T15:30:54.511Z info: Testing connection to Qlik Sense Cloud...
2024-02-16T15:30:55.187Z error: LIST COLLECTIONS 1 (message): Request failed with status code 401
2024-02-16T15:30:55.187Z error: LIST COLLECTIONS 1 (error code): 401="Unauthorized"
➜  butler-sheet-icons

Which makes sense, ´an-invalid-key` is obviously not a proper/valid API token.

[bskemp01]

ok. with the updates to the programs here is my new screenshot. i hope this information helps you