https://prefect.io
Join Slack
is there a way to have `create_flow_run` not base the new flow’s name off of the current flow withou...
# ask-community
d
is there a way to have 
create_flow_run
not base the new flow’s name off of the current flow without passing 
run_name
?
i want the backend to generate a 
run_name
for me, but if i pass any empty value, 
create_flow_run
will override it with it’s 
{current}-{flow.name}
value
this is especially noticeable with cyclic flows that restart themselves on run end. they’ll constantly be appending on their name: • 
foo-bar
• 
foo-bar-flowname
• 
foo-bar-flowname-flowname
• 
foo-bar-flowname-flowname-flowname
etc
it looks like i could delete/replace the 
flow_run_name
from the context, but that feels a bit hacky/dangerous?
k
Man that’s tricky. Maybe use the 
RenameFlowRun
task inside the subflow and 
flow-date
or something like that?
d
i’ll likely use the date like your suggestion. however, on prefect’s side replacing the default value to be some well-known sentinel and checking against that should be backwards compatible and allow for 
run_name=None
to mean “backend make it for me please”
k
@Marvin open “create_flow_run should name flows with the adjective-animal combination”
m
d
🥳
fwiw 
prefect.context["flow_run_name"] = None
does work
k
Yo…that’s clever!
4 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by