Skip to content

Draft: Bind create_vulnerability_report to read_vulnerability

mo khan requested to merge mokhax/412693/create-vulnerability-export into master

What does this MR do and why?

In %17.0 we are introducing a breaking change that removes the ability to change the state of a vulnerability away from the Developer role. This change will allow organizations to maintain a separate role for these privileges via a custom role. To accommodate the upcoming change this MR moves the create_vulnerability_export ability away from the Developer role and binds it to the read_vulnerability ability. The work in this MR is a continuation of the work started in !136121 (merged).

#412693 (closed)

MR acceptance checklist

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

Merge request reports