Switch airbrake mgmt to defra-ruby-alert #657
Merged
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
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. These changes are the first step in switching the WCR service to using it.
This includes updating the engine config to cover defra_ruby_alert.
Cruikshanks
added a commit
to DEFRA/waste-carriers-front-office
that referenced
this pull request
Feb 4, 2020
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. The main changes to enable this have been applied to the [waste-carriers-engine](DEFRA/waste-carriers-engine#657). These changes finalise the implementation for the front-office, switching out requiring and configuring Airbrake directly, to passing config details through to the WCR engine for it to do it.
Cruikshanks
added a commit
to DEFRA/waste-carriers-back-office
that referenced
this pull request
Feb 4, 2020
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. The main changes to enable this have been applied to the [waste-carriers-engine](DEFRA/waste-carriers-engine#657). These changes finalise the implementation for the front-office, switching out requiring and configuring Airbrake directly, to passing config details through to the WCR engine for it to do it.
Cruikshanks
added a commit
to DEFRA/waste-carriers-back-office
that referenced
this pull request
Feb 4, 2020
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. The main changes to enable this have been applied to the [waste-carriers-engine](DEFRA/waste-carriers-engine#657). These changes finalise the implementation for the back-office, switching out requiring and configuring Airbrake directly, to passing config details through to the WCR engine for it to do it.
|
Also linked to DEFRA/waste-carriers-back-office#647 and DEFRA/waste-carriers-front-office#395 which are currently referring to this branch and have been updated to use defra_ruby_alert via the engine rather than config Airbrake directly. |
irisfaraway
approved these changes
Feb 7, 2020
Cruikshanks
added a commit
to DEFRA/waste-carriers-front-office
that referenced
this pull request
Feb 7, 2020
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. The main changes to enable this have been applied to the [waste-carriers-engine](DEFRA/waste-carriers-engine#657). These changes finalise the implementation for the front-office, switching out requiring and configuring Airbrake directly, to passing config details through to the WCR engine for it to do it.
Cruikshanks
added a commit
to DEFRA/waste-carriers-back-office
that referenced
this pull request
Feb 7, 2020
Whilst working on an issue for the [Flood Risk Activity Exemptions service](https://github.com/DEFRA/ruby-services-team/tree/master/services/frae) we came across an [issue](DEFRA/flood-risk-engine#312) with Airbrake. We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR. So for reasons outlined in [FRAE PR 312](DEFRA/flood-risk-engine#312) we came up with [defra-ruby-alert](https://github.com/DEFRA/defra-ruby-alert). The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios. The main changes to enable this have been applied to the [waste-carriers-engine](DEFRA/waste-carriers-engine#657). These changes finalise the implementation for the back-office, switching out requiring and configuring Airbrake directly, to passing config details through to the WCR engine for it to do it.
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.
Whilst working on an issue for the Flood Risk Activity Exemptions service we came across an issue with Airbrake.
We wanted to add a new Rake task, and we wanted to apply our new pattern of ensuring Airbrake is closed when the task exits to ensure any errors are reported. The problem was due to the age of the Airbrake gem being used this caused an error in FRAE we hadn't seen in WEX and WCR.
So for reasons outlined in FRAE PR 312 we came up with defra-ruby-alert. The idea is going forward this will provide a single interface for configuring Airbrake and ensure the pattern of making sure all exceptions are reported before an app closes is applied consistently in all scenarios.
These changes are the first step in switching the WCR service to using it.