Migrate from `redis` to `valkey`

[valentijnscholten]

Since the license change at Redis the fork ValKey has become widely popular and is backed by industry giants such as AWS. AWS is advising to use ValKey over Redis and is using lower prices for ValKey compared to Redis.

Defect Dojo will migrate over to ValKey, we're currently investigating the migration paths. At first sight it looks like the existing Docker volume can just be used by the ValKey container.

• https://valkey.io/topics/migration/

[mtesauro]

We are also fortunate that DefectDojo has only kept ephemeral data in Redis so as long as you shut down DefectDojo correctly, there shouldn't be data you need to actively move.

[valentijnscholten]

The queue of unprocessed celery tasks is stored on disk on shutdown. So any dedupe tasks, notification tasks, product grading tasks etc not yet processed are picked up again after the restart. Even though the data itself in these task is ephermal, I think it would be best if these "task triggers" are not lost.

[mtesauro]

The queue of unprocessed celery tasks is stored on disk on shutdown. So any dedupe tasks, notification tasks, product grading tasks etc not yet processed are picked up again after the restart. Even though the data itself in these task is ephermal, I think it would be best if these "task triggers" are not lost.

Fair point. I was trying to say that with "shutdown correctly" that Celery has run dry but short of watching the container logs, I don't think we surface this anywhere.

So I agree that it would be best to avoid loosing the task triggers. 👍