You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a flow adds itself to a context, it does so under the flow key (in other words, it becomes available at prefect.context.flow). This has the potential to override a possibly common user-supplied context value. Instead, any automatically-set context value (including flows, as described here, and all settings used by FlowRunner and TaskRunners, like parameters) should be put under a key, perhaps __prefect__. This way they won't shadow user variables.
The text was updated successfully, but these errors were encountered:
(inspired by work in #18)
Currently, when a flow adds itself to a context, it does so under the
flow
key (in other words, it becomes available atprefect.context.flow
). This has the potential to override a possibly common user-supplied context value. Instead, any automatically-set context value (including flows, as described here, and all settings used byFlowRunner
andTaskRunners
, likeparameters
) should be put under a key, perhaps__prefect__
. This way they won't shadow user variables.The text was updated successfully, but these errors were encountered: