Today, when we release beam we also release a set of containers. Over time, these containers can accrue vulnerabilites, many of which can be remediated by recreating the containers without changing the source, since this can enable things like updating the underlying container base image (where most vulnerabilities come from). We should publish these regularly as snapshots which can be consumed on demand as needed from our testing project.
Steps:
[ ] Add a workflow which allows us to manually do this
[ ] After verifying that works, set up the workflow to automatically do this based on the configured last RC
[ ] Update the release guide to explain how/when to update these values
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
damccorm
commented
1 week ago
What would you like to happen?
Today, when we release beam we also release a set of containers. Over time, these containers can accrue vulnerabilites, many of which can be remediated by recreating the containers without changing the source, since this can enable things like updating the underlying container base image (where most vulnerabilities come from). We should publish these regularly as snapshots which can be consumed on demand as needed from our testing project.
Steps:
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components