Sentry for a CLI client

Is there an authentication mechanism for shipping the DSN with the client application (CLI, in this case)?

For ex: I tried triggering an error to the following DSN –

… and it looks like the report was successful.

Any help appreciated.

Nope, that’s generally an unsolved problem. You can also get OAuth credentials from any Twitter app for Android by using apktools or something similar. We could probably avoid putting it directly in the source code of sentry-cli and change our Travis config to insert it during compilation only, but in the end the DSN will land on every user’s device, unavoidably.

Thought so. In my case, the other way I can think of is to build an error reporting HTTP endpoint that works with CLI user’s authentication key that’s unique for the user.

Thanks anyways @untitaker