svix / svix-cli Goto Github PK

Sometimes I get a connection error from the CLI:

Failed to connect to Webhook Relay:
dial tcp: lookup [api.relay.svix.com](http://api.relay.svix.com/) on [::1]:53: read udp [::1]:53254->[::1]:53: read: connection refused

Ideally, it gracefully reconnects and I'm right back to receiving webhooks.

Right now, it crashes and I have to manually restart it.

wait for rate limiting

% svix application update test '{
      "name": "Rock Inc.",
      "uid": "test"
    }'
Error: `svix application update` accepts between 0 and 1 arg(s), received 2. Run `svix application update --help` for usage information.

The arg count is wrong.

This would make the automatic json colorization if TTY functionality more visible and easy to understand.

Would make it much easier for us to dogfood cli changes internally

Brew - macOS
Scoop - windows
Snap? - linux

There's a way to detect whether we are in a TTY or a script. If we are in a TTY we should have color on by default. It's just too good to not have on. :)

Description

When generating an App Portal Url an accessToken and a serverUrl are required to be set. Performing the command below without setting the serverUrl results in a 401 response.

$ svix authentication dashboard "appId"
{
"code": "authentication_failed",
"detail": "Invalid token. Have you set the correct server URL?"
}

Current

Running svix login command queries for token and adds/sets it to the config.toml. It does not ask for a serverUrl. server_url can however be set manually within config.toml

Proposal

• Update docs to include
  export SVIX_SERVER_URL='THE_SERVER_URL'

• Enhance svix login to ask for optional serverUrl. Whether provided or not, server_url within the config.toml should also be set.

See Slack conversation for reference

Run

svix application create --data-name "Test Application" --data-uid "test"
# And again
svix application create --data-name "Test Application" --data-uid "test"

The second one will fail with a 409. We should print the json response (pretty-print). Now we just print nothing.

E.g. http://localhost:8000/webhook/

This is to make it clear that the local url should be a full path rather than http://localhost:8000. It's obvious in retrospect, but the lack of an example just confused me. :)

Hey ya'll,

This sounds like it might fix a bug I'm seeing in the 0.17.0 client: #81

However, I can't seem to access that version through Scoop - is there some missing step from the release process?

scoop status svix
Scoop is up to date.
Everything is ok!

scoop update svix
svix: 0.17.0 (latest version)
Latest versions for all apps are installed! For more information try 'scoop status'

Thanks 🙂