Skip to content

Amend NONE state changes related to DAST Site Validation

Dheeraj Joshi requested to merge djadmin-dast-none-state into master

Related &4871 (closed)

What does this MR do?

This MR

  • amends a newly added NONE state to DAST site validation enum.
  • replaces the wrongly used PENDING state with NONE state
    • NONE signifies a DAST validation does not exist and it's also the initial state for a DAST Site Profile
    • PENDING signifies a DAST validation process has started but not yet picked by the validation service

Screenshots (strongly suggested)

No Visual Changes

Does this MR meet the acceptance criteria?

Conformity

Edited by Dheeraj Joshi

Merge request reports