feat: Support long running pipelines with Step Functions' wait for callback feature. #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
This change enables Pipeline creators to run jobs that take longer than the 15 minute Lambda function timeout by enabling use of Step Functions Task Tokens with VAMS Workflows and Pipelines. Before this change VAMS could only run a Lambda function or Sagemaker Job. Now, a Lambda function can spawn any workload and pass a "Task Token" so that the work can be marked complete in a VAMS Workflow state machine from any authorized compute resource rather than when the Lambda invoked by Step Functions completes. See updated DeveloperGuide.md for more info.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.