CI integration with Github action with RHACS as yaml:
Customer would like to add in workflow a couple of lines of config, using an official Redhat / Stackrox Github action, to which I would pass :

• the Github token
• ACS URL and credentials
• the GCR URL
• the name and version of the image that was just pushed
• maybe there would be several tasks available, but the default one would be "scan".
• a flag indicating if a failure of the step should fail the build or not
• The action would then scan the provided image, based on ACS config, and make the results available in its output . By default, it should fail the build if any violation is found.

• This will benefit the customer in these ways:
  1.out of the box integration, no need to have custom scripts to achieve the same
  2.the RedHat action would be versioned, and we would be able to upgrade regularly without thinking too much.
  3.Github actions are more and more becoming a standard : it's easier to adopt by the organization (from developers to SecOps team) if it's an official image by RedHat rather than a custom action made by an internal platform team.
  4.the benefit is that Github action integration is now an expected feature by most dev teams for all the CI related tools : providing it reassures people that they won't have to spend time for custom CI integration, as most of the specifics will be hidden from the in the official action