Skip to content

fcli fod aviator apply-remediations doesn't explain why some remediations are "skipped" #1022

@kadraman

Description

@kadraman

Current Behavior

After a successful FoD Scan with Aviator enabled and remediations to apply, if we run:

> fcli fod aviator apply-remediations --release "Fortify Demo App:remediation-test" --log-level DEBUG --log-file fcli.log
 Release id  Total remediation  Applied remediation  Skipped remediation  Action              
 194274      16                 13                   3                    Remediation-Applied 

there is not information about why some remediations were "skipped" and there is no information in the log file as to why.

Expected Behavior

When remediations are skipped we need to provide information to the user as to why.
It would probably be beneficial for this command to have a --results-file option or similar which produced a report on what changes were made to each file including why it was skipped for some.

Steps To Reproduce

No response

Environment

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingeffort:lowEasy to implement/fixenhancementNew feature or requestfcli-aviatorAviator-related issuesfcli-fodIssue related to 'fcli fod' commandsprio:mediumMedium priority

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions