Remove native sentry monitor integration (raven config) #446
Conversation
This file contains 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
Replace this integration with an opt-in package, see: [g3w-admin-sentry-monitor](https://github.com/g3w-suite/g3w-admin-sentry-monitor)
Raruto
changed the title
Raruto
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The intent of this pull is to replace this integration with an opt-in package, ref: g3w-admin-sentry-monitor (WIP)
This also to ensure greater flexibility in terms of use (e.g. ensuring that the same sentry settings are applied regardless of the currently installed version of g3w-suite) and clarity towards the end user (eg. being able to set up a custom DSN without drowning in hundreds of g3w-suite settings..)
Related to: g3w-suite/g3w-client#68