Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get Sentry DSN from environment variable #64

Merged
merged 2 commits into from
Nov 14, 2020
Merged

Conversation

timm0e
Copy link
Contributor

@timm0e timm0e commented May 26, 2020

When using the Sentry SDK in Go, it usually also reads the DSN from the SENTRY_DSN environment variable

This way Sentry can be configured from outside the container and one does not need an entrypoint to get the DSN from said environment variable.

timm0e added 2 commits May 26, 2020 11:22

Verified

This commit was signed with the committer’s verified signature.

Verified

This commit was signed with the committer’s verified signature.
@timm0e timm0e requested a review from krallin as a code owner May 26, 2020 09:37
Copy link

@hartwork hartwork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea 👍

@@ -253,6 +253,10 @@ Report errors to Sentry by passing a Sentry DSN:
$ ./supercronic -sentry-dsn DSN
```

You can also specify the DSN via the `SENTRY_DSN` environment variable.
When a DSN is specified via both the environment variable and the command line parameter
Copy link

@hartwork hartwork Aug 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding a comma at the end of this line would help cognitive flow. Just an idea.

Copy link

@Mazyod Mazyod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 I'm all for this feature

@krallin krallin merged commit 8f8ef8a into aptible:master Nov 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants