Skip to content

[CS For Registry] Add registry event info to container scanning report

Description

  1. Add new information to the container scanning report as a registry event for components identified by registry event triggers if the ENV variable introduced in [CS For Registry] Add env variable to identify ... (#443621 - closed) is set.
  2. The new container scanning report should be a valid schema.

User Impact

After the implementation, the newly generated CS file should have an identifier pointing to the instigator of the pipeline job, i.e. registry_event.

Non-functional requirements

  • Update documentation to include a new field.
  • Testing: Add unit tests/specs.

Implementation plan

  1. Add scan.type to container_scanning_for_registry in gl-container-scanning-report.json report if env variable REGISTRY_TRIGGERED is set.
  2. Add test cases.

Verification steps

  1. Set newly introduced env variable.
  2. Run the CS job.
  3. Verify that the CS report has newly introduced instigator identifier.
Edited by Aditya Tiwari