Provide output-only data image for vunnel data #148
Labels
enhancement
New feature or request
Comments
willmurphyscode
pushed a commit
that referenced
this issue
Mar 27, 2024
Bumps [orjson](https://github.com/ijl/orjson) from 3.8.9 to 3.8.10. - [Release notes](https://github.com/ijl/orjson/releases) - [Changelog](https://github.com/ijl/orjson/blob/master/CHANGELOG.md) - [Commits](ijl/orjson@3.8.9...3.8.10) --- updated-dependencies: - dependency-name: orjson dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today the
ghcr.io/anchore/grype-db/dataimage provides a cache of the entire vunnel workspace so that the data can be refreshed keeping both the previous input and output in mind. This is great for daily data syncs, but overkill for daily DB builds, which only require the results from the data cache (a much smaller data set).It would be ideal to provide a
ghcr.io/anchore/grype-db/data-inputor similar image which contains only the result DBs of the vunnel runs, or that is, only what is needed for input into the grype-db build (naming will be fun here). This way downstream consumers (such as acceptance tests, staging DB builds, and production DB builds) can be done without needing to download several GB of data.The text was updated successfully, but these errors were encountered: