Restricting DAST Variables Mutation Payload Schema

Dheeraj Joshirequested to merge
djadmin-fix-dast-variable-update into master

What does this MR do and why?

This MR addresses issues with DAST optional variables:

  1. [Frontend] Restricts the mutation payload schema to only include variable and value keys.
  2. [Frontend] Ensures an empty array is passed to properly delete existing optional variables.
  3. [Backend] Fixes a backend 500 error [!177610 (merged)\]

The feature is behind a feature flag

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

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

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Dheeraj Joshi

Merge request reports