Add deployment approval lifecycle webhook events

What does this MR do and why?

Add deployment approval lifecycle webhook events

Extend the existing Deployment webhook (deployment_events flag) with three new event triggers:

  • status: "blocked" when a deployment enters the awaiting-approval or manual-action state (CE and EE).
  • status: "approved" when an approver records an approval, with new top-level approver and approval fields populated from User#hook_attrs and Deployments::Approval#hook_attrs (EE only).
  • status: "rejected" mirrors approved for the rejection action (EE only).

The changes are additive on the wire: existing receivers see no difference for the pre-existing lifecycle events. status continues to reflect the new state of the entity driving each event - the deployment row for lifecycle transitions, the approval row for approval actions.

Includes documentation of the new event variants, the redaction behavior of `approver.email`, and the multi-event sequences a receiver will observe across an approval flow.

Refs #441402

Changelog: added

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #441402

Merge request reports

Loading
Loading