Introduce support for event-triggered workflows#1271
Conversation
|
Let me know when this is ready for review. Happy to look and provide feedback whenever you want (I am out on the week of the 19th so responses that week may be delayed). |
There shouldn't be much to review but I will give you a heads up. |
|
Sounds good. And yes, I will probably defer to you for any and all argo stuff :). It's just the common decorator(s)/parameter changes that I will review so yes, shouldn't take long. If you get that part done first, I can try to implement internally and see if I hit any snags as well (so we have a bit more confidence that we are all good). |
dd318b5 to
69473f8
Compare
romain-intel
left a comment
There was a problem hiding this comment.
I have not reviewed any of the airflow/argo/step_functions code. I also need to review more the decorators (wrong computer right now to review based on what we currently have). This is therefore an initial high-level review. Happy to talk more.
romain-intel
left a comment
There was a problem hiding this comment.
More comments but converging :). I'll try to have the alias thing shortly. Also, please add typing and documentation to all public facing APIs and classes in a manner consistent with the rest of the documentation.
cd3a2bc to
89b13e8
Compare
romain-intel
left a comment
There was a problem hiding this comment.
Not done reviewing yet but initial comments to get them to you as fast as possible.
84faed7 to
62f7089
Compare
romain-intel
left a comment
There was a problem hiding this comment.
Ok. I think I am done. I have not reviewed any of the airflow, argo, sfn or kube portions instead focusing on the common changes.
Items remaining
draft docs - https://github.com/Netflix/metaflow-docs/pull/86/files