-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Labels
bugSomething isn't workingSomething isn't workingeffort:mediumMedium effort needed to implement/fixMedium effort needed to implement/fixfcli-fodIssue related to 'fcli fod' commandsIssue related to 'fcli fod' commandsprio:highHigh priority; important new feature or bug fixHigh priority; important new feature or bug fix
Description
Current Behavior
When running fcli fod issue update you can provide --developer-status and --auditor-status as follows:
Command options
--auditor-status=<auditorStatus>
The Auditor Status to set for the vulnerabilities.
Allowed values: PendingReview,
RemediationRequired, RemediationDeferred,
RiskMitigated, RiskAccepted, NotAnIssue.
--dev-status=<developerStatus>
The Developer Status to set for the
vulnerabilities. Allowed values: Open,
InRemediation, Remediated, WillNotFix,
ThirdPartyComponent.
However these are just the default tenant values and you can create you own custom values for each of these fields.
The current implementation would not support this.
Expected Behavior
It is suggested that --developer-status and --auditor-status are provided as free-form text fields that are then validated by the command to determine if they have acceptable values (by using FoD attributes API).
Since many issues can potentially be updated, it is recommended that some form of caching is used to prevent multiple redundant API calls.
Steps To Reproduce
No response
Environment
Anything else?
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingeffort:mediumMedium effort needed to implement/fixMedium effort needed to implement/fixfcli-fodIssue related to 'fcli fod' commandsIssue related to 'fcli fod' commandsprio:highHigh priority; important new feature or bug fixHigh priority; important new feature or bug fix