parameter_flow.py. To deploy a version to AWS Step Functions, simply run
Parametersas the key -
step-functions createagain, it will create a new version of your flow on AWS Step Functions. The newest version becomes the production version automatically (due to the consistency guarantees provided by AWS Step Functions, it might be a couple of seconds before this happens). If you want to test on AWS Step Functions without interfering with a production flow, you can change the name of your class, e.g. from ParameterFlow to ParameterFlowStaging, and
step-functions createthe flow under a new name.
--max-workersoption. For instance,
step-functions create --max-workers 500allows 500 tasks to be executed concurrently for every foreach step.
run --max-workersthat is used to limit concurrency outside AWS Step Functions.
step-functions createis called,
deployment_infois evaluated which captures your user name and the time of deployment. This information remains constant on AWS Step Functions, although the user may override the default value.
contextobject is passed to any function defined in Parameter. It contains various fields related to the flow being deployed. By relying on the values passed in context, you can create generic deploy-time functions that can be reused by multiple flows.
@scheduledecorator. This flow is triggered hourly:
@schedulein one of the following ways:
@schedule(weekly=True)runs the workflow on Sundays at midnight.
@schedule(daily=True)runs the workflow every day at midnight.
@schedule(hourly=True)runs the workflow every hour.