Feat(gateway): sentry

[vertex451]

Resolves #184
Related to openmfp/helm-charts#758

Changes

Replaced envconfig with viper in both Listener and Gateway

• Used fields from the default config when possible
• Set default values in root init func.
  P.S. I am not sure about the config struct, currently I am using a single config for both Gateway and Listener, but we can split it into two different configs if it makes more sense. It will affect the config initialization thought.

Added sentry.CaptureError on the most crucial parts.

Note: This PR doesn't cover Sentry integration in the Listener.
Also, I ignored errors coming from user input, instead I focused on the service level errors that we would like to monitor, namely:

• Failed to start watching files
• Failed to handle file event because it is not known.
• Failed to process file change(failed to read from file or to create a GraphQL schema)
• Failed to Serve HTTP because handler is not found
• Subscription errors:
• • start a subscription
• • cast event to unstructured
• • determine file changes

TBD

• Sentry integration - I added needed code, but we still need to connect the deployment on dev, int, prod to the Sentry Dashboard.

[aaronschweig]

Please have a look at https://github.com/openmfp/account-operator/blob/main/cmd/root.go#L31-L53 to see how to properly implement the new configuration with viper

[pteich]

You can not use the already closed ctx here. You need to create a new context (with a timeout maybe).

[vertex451]

Good catch, I created a new context with timeout from the default config.