Is there a way to use

@schedule

with different parameters being passed into the flow? Is

Config

the only option? We have an existing setup where a single Flow is being called with different parameters and migrating it to use

Config

is non-trivial

not per se, but a workaround is to use event-triggering -

@trigger

or

@trigger_on_finish

- pass parameters via events, and implement

@schedule

-like functionality in the start step (e.g. check if the time matches the parameter passed)

hmm IIRC those assume you run Argo Workflows, correct?

right, if you are on SFN you can use

Deployer

to trigger a flow with parameters

Will look again at Deployer. For SFNs I thought that it only allowed creation of new deployments/SFNs, since

from_deployment

is supposed to be Argo only. Deployer would support • looking up existing deployed SFN • triggering it with runtime-defined parameters?

ah right, it works only for new deployments with SFN currently. You can call

step-functions trigger

on the command line for the same effect

@straight-shampoo-11124 thanks for the responses. Can I ask, do you know if there is a roadmap/plan for Metaflow + SFN improvements?

it'd be great if you can add a comment about your use case in this ticket so we can prioritize it accordingly. We are gauging how much need there is for it (since it takes some effort to implement - PRs are welcome of course 🙂 )