-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Map state #184
Implement Map state #184
Conversation
69e0eed
to
9e773a1
Compare
|
||
module Floe | ||
class Workflow | ||
class ItemProcessor < Floe::WorkflowBase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool 👍... Was wondering how you were going to implement it, since it's like a sub workflow
6a550cd
to
da41408
Compare
f1f9fba
to
b495db2
Compare
7381a42
to
ae1edf1
Compare
Do we want to leave the |
Just saw this: The loop thing I pointed to above gives us concurrent requests. |
When you have an itch for floe... Could you swap the first commit with the second commit? e.g.: master...kbrock:floe:add_map_state When I did this I lost attribution (otherwise I'd put in a PR for the first commit) Only commits 1 and 2 changed, and they did not change functionally. possible changes:
|
ec0bb60
to
000632b
Compare
@kbrock okay I've tested this with a Task in the sub-workflow to verify the event handling works for containers run from the child workflows and it was successful, taking out of WIP |
Checked commits agrare/floe@6318b74~...1ca1251 with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint |
Added - Add WorkflowBase base class for Workflow (#279) - Add tool for using the aws stepfunctions simulator (#244) - Implement Map state (#184) - Add Map State Tolerated Failure (#282) - Run Map iterations in parallel up to MaxConcurrency (#283) - Implement Parallel State (#291) Changed - More granular compare_key and determine path at initialization time (#274) - For Choice validation, use instance variables and not payload (#277) - Return ExceedToleratedFailureThreshold if ToleratedFailureCount/Percentage is present (#285) Fixed - Fix case on log messages (#280) - Handle either ToleratedFailureCount or ToleratedFailurePercentage (#284)
Very WIP, right now just testing payload validation and input processingJust a little WIP nowDepends on:
TODO: