Our e2e scripts would gain some additional coverage to prevent bad code going out, if we were to test this path in our scripts.

Unfortunately there are two paths through e2e, one we run locally with "make e2e": https://github.com/openshift/sippy/blob/main/scripts/e2e.sh

And the path we use in CI: https://github.com/openshift/sippy/tree/main/e2e-scripts

If we could expand these to stand up a redis pod, then run the two loaders for comp readiness cache and then regression tracker, I'll include a couple sample commands from local history to help show what we would run in these scripts:

podman run --name sippy-redis --restart=always -p 6379:6379 -d redis

./sippy load --log-level=info --database-dsn="$DSN" --google-service-account-credential-file ~/creds/openshift-gce-devel-c4aa95abfa58.json --init-database  --redis-url="redis://192.168.86.2:6379" --views config/views-dev.yaml --loader component-readiness-cache --loader regression-tracker