-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
aws-stepfunctions-tasks: support revision id in StepFunctionsStartExecution #26532
Comments
StartExecution only accepts qualified state machine ARNs for the startMachineArn API parameter, not a revisionId. The scope of this issue should be to support invoking a state machine version or alias in StepFunctionsStartExecution. Another proposed solution is to add |
Thanks for the additional context and clarification @wong-a |
Describe the feature
Step Functions now supports Versions and Aliases.
I would like to have the
tasks.StepFunctionsStartExecution
link to a specific state machine revision ID.Use Case
The use case is where there is a parent and child nested step function. If a deploy occurs that updates the nested step function, this may break long running executions of the parent. By linking the parent step function to a revision of the child step function, we can prevent many such breakages.
Proposed Solution
Currently tasks.StepFunctionsStartExecution accepts a
StateMachine
. I would instead like to pass thestateMachineRevisionId
which was added here: #26443Other Information
No response
Acknowledgements
CDK version used
Latest
Environment details (OS name and version, etc.)
Amazon Linux 2
The text was updated successfully, but these errors were encountered: