📊Tracking: Step Functions #6489
Assignees
Labels
@aws-cdk/aws-stepfunctions
Related to AWS StepFunctions
@aws-cdk/aws-stepfunctions-tasks
management/tracking
Issues that track a subject or multiple issues
Comments
ccfife
added
the
management/tracking
shivlaks
changed the title
shivlaks
changed the title
mergify bot
pushed a commit
that referenced
this issue
May 20, 2020
… and SQS (#7946) merge functionality currently modeled under task and state into a single object that represents a task state as an abstract class. Service integrations extend the base class and add service specific configuration, metrics, and policies. this commit introduces the "new" service integrations for Lambda, SNS, and SQS Motivation: The current service integrations that are offered in `aws-stepfunctions-tasks` all currently implement a `bind()` method and contribute a portion of the configuration that creates a `Task` state. However, it's often useful to configure state level properties such as paths, retries, errors based on the service integration and the pattern that has been requested. Implementation: * Duplicate the current `Task` class and merge the properties of a task state and a task service integration into a new abstract base class. * Concrete implementation per service integration class where all of the best practices and user intents can be encoded * After all the service integrations have been migrated, we will want to retire the `Task` class as well since we don't want it to be instantiated. Paves the way for: #6715 by simplifying the invocation of service integration calls. We would be able to start adding properties such as retries and errors. #6489 where we will be making service integrations consistent ### End Commit Message ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
karupanerura
pushed a commit
to karupanerura/aws-cdk
that referenced
this issue
May 22, 2020
… and SQS (aws#7946) merge functionality currently modeled under task and state into a single object that represents a task state as an abstract class. Service integrations extend the base class and add service specific configuration, metrics, and policies. this commit introduces the "new" service integrations for Lambda, SNS, and SQS Motivation: The current service integrations that are offered in `aws-stepfunctions-tasks` all currently implement a `bind()` method and contribute a portion of the configuration that creates a `Task` state. However, it's often useful to configure state level properties such as paths, retries, errors based on the service integration and the pattern that has been requested. Implementation: * Duplicate the current `Task` class and merge the properties of a task state and a task service integration into a new abstract base class. * Concrete implementation per service integration class where all of the best practices and user intents can be encoded * After all the service integrations have been migrated, we will want to retire the `Task` class as well since we don't want it to be instantiated. Paves the way for: aws#6715 by simplifying the invocation of service integration calls. We would be able to start adding properties such as retries and errors. aws#6489 where we will be making service integrations consistent ### End Commit Message ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Hi, I wonder how is the best way to track the progress/plans for further integrations. For example, to invoke an API Gateway from stepfunction. |
|
@mariobittencourt Check for open issues with the @aws-cdk/aws-stepfunctions-tasks label. There is already an issue tracking API Gateway support that has some PRs waiting for review. #11566 |
|
Thank you @wong-a. I started tracking them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add your +1 👍 to help us prioritize high-level constructs for this service
Overview:
The
@aws-cdk/aws-stepfunctionspackage contains constructs for building serverless workflows using objects. Use this in conjunction with the@aws-cdk/aws-stepfunctions-taskspackage, which contains classes used to integrate with other AWS services.AWS Docs
Maturity: Experimental
See the AWS Construct Library Module Lifecycle doc for more information about maturity levels.
Open issues
Implementation:
CDK API Reference
aws-stepfunctionsandaws-stepfunctions-tasksmodulesRunJobon ECS #8451)Issue list:
This is a 📊Tracking Issue
The text was updated successfully, but these errors were encountered: