Dismissing vulnerability record on an MR is not triggering webkook events
Summary
- Configure webhook events via https://docs.gitlab.com/user/project/integrations/webhook_events/#vulnerability-events
- Change vulnerability status in an MR to Confirmed or Resolved
- A webhook event is triggered.
- Change vulnerability status in the same MR to Dismissed
- A webhook event is not triggered.
- Undo the dismiss,
- A webbhook is triggered
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
This should trigger dismiss vulnerabiltiy webhoook event as in all other vulnerability state changes it does
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.