search

pusher / cli

A CLI for Pusher (beta)
51 stars 6 forks source link

Pusher CLI for collaborators #29

Open BrandonShega opened 6 years ago

BrandonShega commented 6 years ago

Is there any way to get the pusher CLI to work correctly for collaborators? Currently collaborators are only able to see apps that they have created themselves and not ones given access to through collaborations.

jameshfisher commented 6 years ago

Unfortunately not. I'll create an internal ticket to track this, because the fix is to one of our systems internally. Thanks for reporting!

aenkya commented 5 years ago

Any update on this?

hakunin commented 5 years ago

What a joke, we'll just have to migrate to a competitor.

damdo commented 5 years ago

Hey @hakunin @Elbertbiggs360 @BrandonShega unfortunately this is still on our internal backlog. Could you describe what features of the CLI your team is using, or wants to use, collaboratively? This would help us prioritize which features we need to add collaborator access to first. Thank you all.

BrandonShega commented 5 years ago

Our biggest use is for collaborators to be able to trigger and subscribe from the CLI, using the admin portal, at least with the amount of messages we send and receive, is basically impossible. It usually just ends up locking up after a few seconds of monitoring it.

hakunin commented 5 years ago

I just needed to see what is the message flow so I can debug what's eating our resources. None of the logging integration services you provide provides any info on what event names are sent and the CLI does not seem to provide a way to listen to all the channels (we use private channels I can't listen to them one by one, I need to listen to all). The web UI simply dies after a few seconds when the even batch hit.