narrow-waitress-79414
03/12/2024, 11:10 PMstale-florist-77883
03/12/2024, 11:52 PM--run-id-file option when triggering the workflow. When you list help, this is the description:
--run-id-file TEXT Write the ID of this run to the file
specified.
Then you can use the id from the file to monitor the run using the metaflow client.stale-florist-77883
03/12/2024, 11:53 PMstale-florist-77883
03/13/2024, 12:00 AMnarrow-waitress-79414
03/13/2024, 8:07 AMstale-florist-77883
03/13/2024, 8:23 AMpython run.py argo-workflows trigger --run-id-file xyz . I am not sure, whether something like this is possible with ArgoEvent.publish.narrow-waitress-79414
03/13/2024, 8:25 AMnarrow-waitress-79414
03/13/2024, 8:26 AMstale-florist-77883
03/13/2024, 8:28 AMArgoEvent.publish finishes. Maybe somebody here knows how to query the runs using that id.narrow-waitress-79414
03/13/2024, 8:30 AMelegant-lamp-40213
03/13/2024, 9:13 AMArgoEvent.publish().
The simplest solution, as of now and to the best of my knowledge, to get lineage from the parent flow is to trigger the child flow on the commandline.
Otherwise, you may be able to use the Metaflow Client, to go through all runs and find those that have been triggered by your event. This did not sound great for my use case, but maybe it makes sense for yours. It may help if you make sure your flow would be tagged with some ID from the triggering event, as you may filter runs on this tag.narrow-waitress-79414
03/13/2024, 9:19 AM