Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Leverage Argo's new workflow persistence storage #86

Open
MyleneSimon opened this issue Sep 23, 2019 · 0 comments
Open

Leverage Argo's new workflow persistence storage #86

MyleneSimon opened this issue Sep 23, 2019 · 0 comments
Assignees
@Samiasa
Labels
feature New feature or request
Milestone
3.1.0

Comments

@MyleneSimon
Copy link
Collaborator

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Samiasa Samiasa

Labels
feature New feature or request
Projects
None yet
Milestone
3.1.0
Development

No branches or pull requests
2 participants
@MyleneSimon @Samiasa