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

ENH: Provide a way to conditionally disable the raygun handler. #65

Merged
merged 1 commit into from Nov 10, 2021

Conversation

GuySartorelli
Copy link
Member

There are situations where it may be useful to have the SS_RAYGUN_APP_KEY environment variable set without automatically sending all exceptions to Raygun.

In particular, we have a use case where we don't want errors sent to raygun in our test and QA environments usually, but we want to be able to run a BuildTask to trigger an exception that does get sent to raygun in those environments as a quick test that changes we have made do what we expect them to in regards to error monitoring.

Copy link
Member

@madmatt madmatt left a comment

Choose a reason for hiding this comment

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

Thanks @GuySartorelli, this looks good. If you're providing this, could you please show an example of overriding this in the README (e.g. I presume you're calling Config::modify() within your BuildTask?)

Other than that, the change looks good to me.

@GuySartorelli
Copy link
Member Author

Commenting in case it's not clear: Requested changes have been made.

@michalkleiner
Copy link

@GuySartorelli please rebase on master as I merged the other PR, then I can merge it.

There are situations where it may be useful to have the `SS_RAYGUN_APP_KEY` environment variable set without automatically sending all exceptions to Raygun.
@GuySartorelli
Copy link
Member Author

@michalkleiner I've rebased on master.

@michalkleiner michalkleiner merged commit 56fb8f1 into silverstripe:master Nov 10, 2021
@GuySartorelli GuySartorelli deleted the feat/disable-handler branch November 10, 2021 09:38
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

3 participants