Epic Goal

• Report warnings to users as part of status updates to SCM systems

Why is this important?

In StoneSoup, many of the tools we use for scanning can emit warnings that should prompt developers to take action. We want to surface these messages to the developer in GitHub, so they can take action either in the pull request, or later on as follow up work.

These warnings otherwise should not "fail" the pipeline and block merge or othewise report failure to the user.

Scenarios

1. Report SAST scan results
2. Report container image scan results

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• Support and SRE teams are provided with enough skills to support the feature in production environment