Grype DB save/cache fails during matrix jobs

[saisatishkarra]

Summary

• The Grype cache in matrix jobs requires unique cache key lock to be acquired while saving cache
• Key: <run_id>_<attempt_id> is not UNIQUE during matrix jobs and requires a fix to override / specific key from downstream workflows.

Options

1. Skip cache by default and always leverage updated cdn

• As an emergency failurein case of CDN failures, there won't be caches since they are expired and skipped

2. Option to override default [<run_id>_<attempt_id>] to make it save unique caches in matrix job
   a. specify option to override cache key as input
   b. Detect if running in matrix contex and generate unique caches based on some prameter.

• Either way, this is also NOT recommended since multipple cache keys might exhaust github default cache limits of 10GB since each file is 150MB and will be unique for run and attempt and each item in matrix

3. Host a mirror as Kong repo and use this URL

• Overhead of effort and maintenance to maintain a list of updated offline grype dbs and consume them