feat: save a copy of capture-area.geojson as an artifact for Argo Workflows TDE-1045 #860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In order to allow Argo Workflows UI to expose a file to the user, the file has to be stored in the local machine. The workflows can then pulled the file as an artifact output. linz/topo-workflows#443
Modification
Save a copy of
capture-area.geojson
file in a different path than the one linked to the STAC Collection.Another option would be to only save the file locally and let Argo Workflow to save it to the target directory. I haven't choose that option to monitor AWS issues from the application rather than from Argo.
Checklist