Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Put parameters into context inside of a flow run
See original GitHub issueWhen a flow runner is in a cloud context it makes a call to the client’s get_flow_run_info function. That call queries for the parameters, version, and current_state. The parameters however are not used. Inside the flow runner it can take those parameters (from its flow_run_info object that it creates) and set it in the context here -> https://github.com/PrefectHQ/prefect/blob/master/src/prefect/engine/flow_runner.py#L189 if there are no other parameters passed into the runner.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I vote for #4 as well – in general I always prefer the “more recently provided” option. For example auth credentials passed immediately > auth credentials in env var > auth credentials in file system. By that logic, parameters passed immediately to the run() function should take precedence over ones that were presumably set a while ago and are being loaded from db
I would vote for prioritizing kwarg over DB because kwarg seems more manual to me as opposed to DB being set once and automatically loaded