oncall-engine/engine/apps/integrations
Innokentii Konstantinov c733d8b9f2
Cleanup ScenarioStep (#1213)
# What this PR does
This PR cleanup ScenarioStep. It's needed to simplify moving Slack to
the messaging backends in future.

1. Introduce AlertGroupSlackService to move logic from ScenarioStep.
Also it allowed to get rid of importing ScenarioSteps in the code not
related to processing of slack callbacks.
2. Remove tags from ScenarioSteps, they are unused.
3. Remove ScenarioStep.dispatch method. It just was calling
ScenarioStep.process_scenario.
4. Remove "action" param from process_scenario, it was unused.
5. Remove creation of SlackActionRecord on handling SlackEvents. We are
not using it, but it generates INSERT query on most of the user-slack
interactions.
6. Remove "random_prefix_for_routing" from ScenarioStep, it was unused.
## Which issue(s) this PR fixes

## Checklist

- [ ] Tests updated
- [ ] Documentation added
- [ ] `CHANGELOG.md` updated

---------

Co-authored-by: Joey Orlando <joey.orlando@grafana.com>
2023-02-21 20:22:11 +01:00
..
metadata Conform URLs (#281) 2022-07-25 09:12:50 -06:00
mixins Org soft-delete (#1073) 2023-01-05 12:42:55 +08:00
templates Add escalation chain option when creating a direct page alert group (#1143) 2023-01-18 12:58:26 -03:00
tests Allow multiple database and celery broker types (#582) 2022-10-04 09:25:53 +01:00
__init__.py World, meet OnCall! 2022-06-03 08:09:47 -06:00
middlewares.py Add middleware to catch exception for missing integration, reduce spamminess of logs 2022-10-13 17:18:22 -06:00
tasks.py Cleanup ScenarioStep (#1213) 2023-02-21 20:22:11 +01:00
urls.py World, meet OnCall! 2022-06-03 08:09:47 -06:00
views.py 1.1.5.5 -> dev (#1060) 2023-01-03 11:57:16 +08:00