Configure Sentry DSN for hackbot-api#6372
Draft
suhaibmujahid wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sets the Sentry DSN for the hackbot-api service so error reporting is actually enabled.
The Sentry SDK was already wired up in
app/main.py(behind anif settings.sentry_dsn:guard) andsentry-sdkis already a dependency, butsentry_dsndefaulted toNone, sosentry_sdk.init()was never called. This sets the DSN as the config default, matching thereviewhelper-apiconvention (a Sentry DSN is a public client key, not a secret). It remains overridable via theSENTRY_DSNenvironment variable.Changes
services/hackbot-api/app/config.py: defaultsentry_dsnto the project DSN instead ofNone.