Create Github issues to re-enable Slack alerts in check_silenced_dags DAG

[stacimc]

Problem

The check_silenced_dags DAG validates the silenced_slack_alerts configuration by checking that each silenced DAG is associated to an open GH issue. If the issue has been closed, the DAG will send a Slack alert indicating that the DAG ought to have error reporting turned back on.

Quote @sarayourfriend from this comment on WordPress/openverse-catalog#643:

It'd be nice if this created a GitHub issue or something that could actually be assigned and tracked or have the maintainers pinged. Or maybe even just left a comment on the issue itself like "Please un-silence the DAG errors". Or maybe both, a new issue and a ping on the old, with the new issue just tracking the work of actually updating the prod configuration.

Just worried a slack ping could easily get lost (especially if lots of people are on vacation or distracted by something else, for example) in a way that a GitHub issue won't, as it acts more like a formal "todo" item.

Description

This would be a fantastic addition to make sure that Slack pings don't get lost. I think opening a new high priority GH issue to track re-enabling alerts is warranted, because by definition we only expect this to happen when an issue was resolved but someone forgot to turn alerts back on.

Implementation

• 🙋 I would be interested in implementing this feature.