Add mend config file for internal scanning purposes - #119
Conversation
Signed-off-by: Brian Hussey <brian.hussey@ie.ibm.com>
| # First scan: OVERRIDE to establish the baseline. | ||
| # Subsequent scans: change to APPEND so previous results are preserved. | ||
| projectName=contextforge-web-ui | ||
| updateType=APPEND |
There was a problem hiding this comment.
LLM asked:
updateType should be OVERRIDE, not APPEND, for this initial scan.
Per the comment on lines 9–10, OVERRIDE is meant for the first scan to establish the baseline, and APPEND for subsequent ones. Since this is the first time whitesource.config is added to the repo, this should ship as OVERRIDE. As-is, the first scan will append to/merge with existing project state on the Mend side instead of establishing a clean baseline.
Suggest: set updateType: OVERRIDE now, then flip to APPEND in a follow-up PR once the baseline scan has run.
There was a problem hiding this comment.
@marekdano thanks.
I've already manually run the first scan, the SPS pipeline will take over the APPEND of all scan results on top of what is already there with every pipeline run.
i.e. the data is already in mend for the subsequent updates to occur.
3 participants
Summary
Add mend config file with requirements to track what is or isn't needed from a scan perspective from within the project.
This sets an identifying name and declares what should be included or excluded from the scan.