Jacob Blanco
04/13/2022, 7:01 AMAnna Geller
Jacob Blanco
04/13/2022, 11:48 PMAnna Geller
Jacob Blanco
04/14/2022, 2:42 AMAnna Geller
It’s much easier to submit too many flow runs accidentally in code than it is in the UIThere are two ways users may run flows: locally (Python client and CLI) and via backend. The latter includes running flows via UI, API, and even CLI. RBAC permissions and concurrency limits apply only to backend runs. Does this answer your question or is it still unclear?
Jacob Blanco
04/14/2022, 11:18 AMAnna Geller
Jacob Blanco
04/14/2022, 12:16 PMAnna Geller
flow.run()
in a Jupyter notebook, this runs only on their local machine, not on EC2 (storage and run configs are ignored when running flows locally)Jacob Blanco
04/14/2022, 12:42 PMwhen the data scientists doIn this case they explicitly wanted to spawn runs in our Prefect EC2 instance since the connectivity with EMR and other AWS resources is already setup and since we are in fintech we are limited in what resources we can interact with directly. I agree with your comment on education, but people make mistakes and I would prefer people feel that they have the freedom to work without necessarily breaking anything in case they make a mistake. I would also prefer that someone with an API key couldn’t DDoS our Prefect instance and kill a bunch of critical jobs. Anyways, thanks for the information. Lots of food for thought here. If I come up with more insights I’ll share back.in a Jupyter notebook, this runs only on their local machine, not on EC2 (storage and run configs are ignored when running flows locally)flow.run()