Init work on publishing final output of "simple" workflow to volume #50

trey-stafford · 2025-01-15T18:52:34Z

resolves #48

trey-stafford · 2025-01-15T18:53:23Z

Next steps:

Address published data in test environment. Cleanup?
Figure out how to determine if a recipe has already published data. Raise an error if so. Provide an option to overwrite.
Consider config for setting up volumes. We can default to qgnet-ogdc-workflow-pvc, but this should be configurable.

Will be used for control flow. We should avoid overwriting existing, published data unless an overwrite flag is given (TODO).

trey-stafford added 3 commits January 15, 2025 17:23

Init work on publishing final output of "simple" workflow to volume

a55b417

Fixup test recipe id (wargo -> argo)

793f523

Create workflow for checking if a recipe has already been published

2e9f997

Will be used for control flow. We should avoid overwriting existing, published data unless an overwrite flag is given (TODO).

trey-stafford force-pushed the publish-outputs-to-volume branch from 25fba91 to 2e9f997 Compare January 16, 2025 00:23

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Init work on publishing final output of "simple" workflow to volume #50

Init work on publishing final output of "simple" workflow to volume #50

trey-stafford commented Jan 15, 2025 •

edited by rmarow

Loading

trey-stafford commented Jan 15, 2025 •

edited

Loading

Init work on publishing final output of "simple" workflow to volume #50

Are you sure you want to change the base?

Init work on publishing final output of "simple" workflow to volume #50

Conversation

trey-stafford commented Jan 15, 2025 • edited by rmarow Loading

trey-stafford commented Jan 15, 2025 • edited Loading

trey-stafford commented Jan 15, 2025 •

edited by rmarow

Loading

trey-stafford commented Jan 15, 2025 •

edited

Loading