GraphQL Subscription triggers through Gitlab::EventStore

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Currently, we trigger GraphQL subscriptions through class methods on GraphqlTriggers.

Perhaps we could leverage the GitLab::EventStore for this instead and keeping a dictionary of events that map to a GraphQL subscription that should be triggered.

Idea came from !80331 (merged)

• @reprazent started a discussion:

  This is not something to address here, but perhaps all of these triggers could go through the Gitlab::EventStore. Then we could have a way to define subscriptions and just map them to a name for GraphQL, rather than having this ever growing file with class methods.

  There's only 3 methods now, so not urgent. Something ~"group::integrations" might want to consider? I'll move this to an issue 😄