Skip to content

Add feature flag check to GraphQL trigger

Patrick Bajao requested to merge 385077-add-realtime-mr-status-change-to-trigger into master

What does this MR do and why?

When realtime_mr_status_change feature flag is enabled, the frontend will subscribe to the mergeRequestMergeStatusUpdated subscription.

If something goes wrong during rollout and the frontend is still connected (user hasn't refreshed the page) even after disabling the feature flag, backend will still trigger the subscription and push updates to the frontend.

To avoid that, this adds the same feature flag check to the GraphQL trigger. This way, when the feature flag gets disabled, backend won't trigger the subscription as well.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #385077 (closed)

Edited by Patrick Bajao

Merge request reports