Add new opsgenie/opsgenie-incidents integration

[calebhailey]

TODO:

• Fork @nixwiz's OSS OpsGenie handler to the https://github.com/sensu org
• Update the OpsGenie handler to sensu-plugin-sdk >= v0.16.x
• Init integration from template (see: https://github.com/sensu/catalog/blob/main/templates)
  • Add README.md
  • Add sensu-integration.yaml
  • Add CHANGELOG.md
• Add logo.png
• Add sensu-resources.yaml
  • opsgenie/opsgenie
  • add a pipeline resource (example: pagerduty/pagerduty-incidents)
  • move configured filters and mutators (if any) from handler(s) to the pipeline resource

[amdprophet]

The API tokens generated via the Opsgenie website do not appear to work with the nixwiz/sensu-opsgenie-handler plugin:

Error occurred with Status code: 403, Message: To perform this action, use an API key from an API integration.

[amdprophet]

I pushed up the WIP branch for this https://github.com/sensu/catalog/tree/jk/add/opsgenie/opsgenie-incidents. I'm waiting for the secrets work to be finished before opening a PR.

[jspaleta]

The API tokens generated via the Opsgenie website do not appear to work with the nixwiz/sensu-opsgenie-handler plugin:

Error occurred with Status code: 403, Message: To perform this action, use an API key from an API integration.

So I'm a little confused by this.

I just spun up an opsgenie trial and created the Sensu integration and obtained an API_KEY and it worked with the existing main branch for the forked repo. No code changes on my part.

We need to reach into there org and get the Sensu integration web tile they offer cleaned up a little but the api key did work for me.

[jspaleta]

Ok the PR is open:
sensu/sensu-opsgenie-handler#1

[asachs01]

@portertech we've got a customer who's stuck using the old betorvs version of the handler and we'd like to get our fork published to Bonsai so that folks can use something that's being actively maintained.