Skip to content
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.

Sign up for GitHub

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

Jump to bottom

aws-stepfunctions-tasks: manage state machine executions as an integrated service #3521

Closed
1 of 5 tasks
wqzoww opened this issue Aug 2, 2019 · 1 comment · Fixed by #3522
Closed
1 of 5 tasks

aws-stepfunctions-tasks: manage state machine executions as an integrated service #3521

wqzoww opened this issue Aug 2, 2019 · 1 comment · Fixed by #3522
Labels
needs-triage This issue or PR still needs to be triaged.

Comments

@wqzoww
Copy link
Contributor

wqzoww commented Aug 2, 2019 •
edited

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.

  • I'm submitting a ...

    • 🪲 bug report
    • 🚀 feature request
    • 📚 construct library gap
    • ☎️ security issue or vulnerability => Please see policy
    • ❓ support request => Please see note at the top of this template.

  • What is the expected behavior (or behavior of feature suggested)?

Step Functions will integrate its own API as a service integration. This allows to start a new execution of a different state machine from the task state of the running state machine.

The list of supported parameters of this new integrated service follows that of our own API StartExecution, including input, name and stateMachineArn.

  • What is the motivation / use case for changing the behavior or adding this feature?

Using nested state machine executions can help users to reduce the complexity of the main workflow and to reuse common processes when building new workflows.

  • Please tell us about your environment:

    • Module Version: v1.3.0
    • Language: TypeScript

  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
@wqzoww wqzoww added the needs-triage This issue or PR still needs to be triaged. label Aug 2, 2019
wqzoww added a commit to wqzoww/aws-cdk that referenced this issue Aug 2, 2019
@wqzoww
feat(aws-stepfunctions-tasks): support step functions state machine e…
2cb50f3 
…xecution from a task state

Step Functions allows to start state machine executions by calling its own API StartExecution as an integrated service. This commit is made to implement this new feature.

The corresponding IAM poliy has been defined and the service principal in the IAM role has been fixed.

Closes aws#3521
@wqzoww wqzoww mentioned this issue Aug 2, 2019
Merged
@JasonMrX
Copy link

JasonMrX commented Aug 2, 2019

This is neat!

wqzoww added a commit to wqzoww/aws-cdk that referenced this issue Aug 3, 2019
@wqzoww
feat(aws-stepfunctions-tasks): support step functions state machine e…
de1ee32 
…xecution from a task state

Step Functions allows to start state machine executions by calling its own API StartExecution as an integrated service. This commit is made to implement this new feature.

The corresponding IAM poliy has been defined and the service principal in the IAM role has been fixed.

Closes aws#3521
wqzoww added a commit to wqzoww/aws-cdk that referenced this issue Aug 8, 2019
@wqzoww
feat(aws-stepfunctions-tasks): support step functions state machine e…
b2003d8 
…xecution from a task state

Step Functions allows to start state machine executions by calling its own API StartExecution as an integrated service. This commit is made to implement this new feature.

The corresponding IAM poliy has been defined and the service principal in the IAM role has been fixed.

Closes aws#3521
@mergify mergify bot closed this as completed in #3522 Aug 9, 2019
mergify bot pushed a commit that referenced this issue Aug 9, 2019
@wqzoww @mergify
feat(aws-stepfunctions-tasks): support step functions state machine e…
ac77990 
…xecution from a task state (#3522)

Step Functions allows to start state machine executions by calling its own API StartExecution as an integrated service. This commit is made to implement this new feature.

The corresponding IAM poliy has been defined and the service principal in the IAM role has been fixed.

Closes #3521
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(stepfunctions): support step functions state machine execution from a task state wqzoww/aws-cdk
2 participants
@JasonMrX @wqzoww