Remove OpenSCAP CVE (OVAL) job from pipeline

Delete OpenSCAP CVE job

We do not need to run the OpenSCAP CVE job within the pipeline as CVE scans are covered by Twistlock and Anchore

Acceptance Criteria

Review removing job with VAT team

• Meet with VAT team to discuss removal of OpenSCAP CVE job

Remove reference to job in README

• Delete LNs139-147
• Delete LN174

Remove job from scanning stage

• Delete openscap-cve.yaml
• Delete openscap-cve-run.sh

Remove references to the OpenSCAP CVE job in templates

• Remove LNs17-18 from default.yaml
• Remove job override in Ubuntu template
• Remove LN18 from distroless.yaml

Remove all references to openscap cve as a dependency

• Check CVEs
• CSV Output
• Documentation
• Upload to S3

Remove use of artifacts from scripts

csv-output.sh

• Cut L12 from the script and replace L23 to output an empty string as the OSCAP_CVE_URL environment variable.

  Need to follow up with the VAT team to remove using this link in the vat import. Once they are not using it, we can remove L23 completely

• Remove oval argument in csv-output.sh

pipeline_wl_compare.py

• Remove references to oscap_cve or oval in Check CVEs e.g LNs120-122 adn LNs132-134

oscap.py

• Remove get_oval function from stages/check-cves/scanners/oscap.py

pipeline_csv_gen.py

• Remove generate_blank_oval_report
• Remove ovf parameter from generate_summary_report function
• Remove generate_oval_report and get_oval_full functions
• Remove use of oval_fail_count

repo_map_vars.sh

• Remove openscap_oval_results
• Remove export of oval_report
• Remove OVAL_Report
• Remove OpenSCAP_OVAL_Results

NOTE:

We do not reference the oscap cve job directly from the development.yaml template, so this does not need to be updated for this change. It is however does need to be updated due to other changes made to the pipeline.