fix: start DAST scan on release with no prior scans - #1068
Closed
jmadhur87 wants to merge 1 commit into
Closed
Conversation
Contributor
|
Superseded by #1070 |
rsenden
added a commit
that referenced
this pull request
Aug 21, 2026
fix: `fcli fod dast-scan start`: Restore fix to allow DAST scan to start if no prior scans exist (lost in Aviator 26.2 merge) (fixes #1068) fix: `fcli fod dast-scan start`: Restore `--vpn` support and 422 active-scan fallback (lost in Aviator 26.2 merge) fix: `fcli fod microservice create`: Re-add non-microservice application guard (lost in Aviator 26.2 merge)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fcli fod dast-scan start threw FcliSimpleException: Unable to start Dynamic scan after 30 attempts on releases that had no previous scans.
Changed the empty-items guard from continue to return null. An empty scan list means no active scan exists for the release, so the method now immediately signals that a new scan can proceed.
fix: start DAST scan on release with no prior scans(#1058 )