stepwise.core

Liking cljdoc? Tell your friends :D

Clojure only.

denamespace-keys
describe-execution
describe-state-machine
ensure-state-machine
kill-workers
offload-select-keys-to-s3
shutdown-workers
start-execution!
start-execution!!
start-workers!
wait-all-exit!!

denamespace-keys^clj

(denamespace-keys response)

source

describe-execution^clj

(describe-execution arn)

source

describe-state-machine^clj

(describe-state-machine arn)

source

ensure-state-machine^clj

(ensure-state-machine name definition)

Create state machine name if not exist; otherwise update with definition.

Arguments: name - state machine keyword name definition - define a state machine using EDN States Language. See README.md

Create state machine `name` if not exist; otherwise update with definition.

Arguments:
name       - state machine keyword name
definition - define a state machine using EDN States Language. See README.md

source raw docstring

kill-workers^clj

(kill-workers workers)

source

offload-select-keys-to-s3^clj

source

shutdown-workers^clj

(shutdown-workers workers)

source

start-execution!^clj

(start-execution! state-machine-name)

(start-execution! state-machine-name {:keys [input execution-name]})

Starts a state machine execution. Non-blocking variant. For blocking, use (start-execution!!)

Starts a state machine execution. Non-blocking variant. For blocking, use (start-execution!!)

source raw docstring

start-execution!!^clj

(start-execution!! state-machine-name)

(start-execution!! state-machine-name {:keys [input execution-name] :as opts})

Starts a state machine execution. Blocking variant. For non-blocking, use (start-execution!)

Starts a state machine execution. Blocking variant. For non-blocking, use (start-execution!)

source raw docstring

start-workers!^clj

(start-workers! task-handlers)

(start-workers! task-handlers {:keys [task-concurrency]})

Starts activity workers in the background. task-handlers is a map of the form {<activity-resource-keyword> <handler fn>}. Where,

<activity-resource-keyword> must match what has been defined in your state machine, see README.md for example. <handler fn> could either be a fn [1] or a map with [:handler-fn :intercepters] keys [2].

References: [1] See https://github.com/Motiva-AI/stepwise#basic-usage [2] See https://github.com/Motiva-AI/stepwise#interceptors

Starts activity workers in the background. `task-handlers` is a map of
the form {<activity-resource-keyword> <handler fn>}. Where,

<activity-resource-keyword> must match what has been defined in your state
machine, see README.md for example.
<handler fn> could either be a fn [1] or a map with [:handler-fn :intercepters]
keys [2].

References:
[1] See https://github.com/Motiva-AI/stepwise#basic-usage
[2] See https://github.com/Motiva-AI/stepwise#interceptors

source raw docstring