VAT Feature Branches

NOTE: This is likely a good exploratory first issue for new team members.

Now that VAT has their endpoints in place, we need to dig through the pipeline code and anywhere that we have a test for what branch you are on. Example:

https://repo1.dso.mil/ironbank-tools/ironbank-pipeline/-/blob/master/stages/build/build-run.sh#L106

One would then delete the branch checks, and then test the code to make sure that it continues to function as expected. We may then update the code to use the VAT endpoints.

DoD

Stages to update

• Lint
  • Remove retrieval of parent image names and hardening manifests
  • Remove SQL query for finding
• Check CVEs
  • This stage will be moved to be run after the VAT stage, using the response JSON to log findings and their status
  • Code parsing scan results will be removed and we will instead need code to parse the VAT API response JSON
  • Create artifacts from this stage
• CSV Output
  • This stage will be moved to be run after the VAT stage, using the response JSON to create CSV files
  • Code parsing scan results will be removed and we will instead need code to parse the VAT API response JSON
• VAT
  • This stage will be moved to run directly after the Scanning Stage
  • The logic to only run this branch of development, needs to be removed
  • Save response from VAT POST API as vat-response.json to be used by Check CVEs and CSV Output