Description
As of version 2.4.0-rc1, Argo supports workflow persistence storage in centralized external database.
We could try to leverage that and have the workflows stored in the WIPP database, so that the storage is persistent and we have workflow status and more directly available in the backend, without having to do extra requests to the Argo API.
Proposal
This new config uses upper.io/db.v3 database adapter, which supports MongoDB, but for now only MySQL and PostgreSQL are provided by Argo as examples of implementation, so we will have to see if using sql database is a requirement.
Description
As of version 2.4.0-rc1, Argo supports workflow persistence storage in centralized external database.
We could try to leverage that and have the workflows stored in the WIPP database, so that the storage is persistent and we have workflow status and more directly available in the backend, without having to do extra requests to the Argo API.
Proposal
This new config uses upper.io/db.v3 database adapter, which supports MongoDB, but for now only MySQL and PostgreSQL are provided by Argo as examples of implementation, so we will have to see if using sql database is a requirement.