Current Behavior
With the implementation of FoD 26.3 there is a new Scan Policy settings that can be configured via the UI or via the API to one of the following values: "Security, DevOps, Classic or FoD(Legacy)". If a user selects "Security" for example in the FoD UI and then a scan is initiated via fcli, github-actions or similar integration, then "Security" settings is not kept - it is overriden/reset back to "FoD(Legacy)"
Expected Behavior
The value of this field should not be changed unless we have explicitly requested it as part of initiating the scan.
Note: this is not available as an option to the fcli fod sast-scan start but will be added. Even when it is added though, if no parameter is specific we should probably still retrieve the server side value and pass it through the /start-scan-with-default API call.
Steps To Reproduce
No response
Environment
Anything else?
No response
Current Behavior
With the implementation of FoD 26.3 there is a new Scan Policy settings that can be configured via the UI or via the API to one of the following values: "Security, DevOps, Classic or FoD(Legacy)". If a user selects "Security" for example in the FoD UI and then a scan is initiated via fcli, github-actions or similar integration, then "Security" settings is not kept - it is overriden/reset back to "FoD(Legacy)"
Expected Behavior
The value of this field should not be changed unless we have explicitly requested it as part of initiating the scan.
Note: this is not available as an option to the
fcli fod sast-scan startbut will be added. Even when it is added though, if no parameter is specific we should probably still retrieve the server side value and pass it through the/start-scan-with-defaultAPI call.Steps To Reproduce
No response
Environment
Anything else?
No response