Track recipe executions in the database.
Currently, we use a recipe's terminal argo workflow's name to check recipe status. This changes on each run, as argo names its workflows in part with a random string. Although it might be possible to query argo for matching workflows based on the recipe name, it's much more straightforward to track executions in the db.
On submitting a new recipe, a database record would be created that ties the recipe to the submitter and includes information like status and any associated argo workflow names. It can also contain information about data output location, etc.
Track recipe executions in the database.
Currently, we use a recipe's terminal argo workflow's name to check recipe status. This changes on each run, as argo names its workflows in part with a random string. Although it might be possible to query argo for matching workflows based on the recipe name, it's much more straightforward to track executions in the db.
On submitting a new recipe, a database record would be created that ties the recipe to the submitter and includes information like status and any associated argo workflow names. It can also contain information about data output location, etc.