-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Support for synchronous express state machines #1
Comments
Hi Steven, There is an open issue in Terraform AWS provider about this - hashicorp/terraform-provider-aws#11348 https://github.com/hashicorp/terraform-provider-aws/blob/master/ROADMAP.md - here it says that it will be taken into account in the near future. Once done we can have support for this in the module. |
Thanks, @antonbabenko! |
I created a PR for this if you'd like to use the changes |
Yes, I will review and merge this later this week. Thanks @cojmcc ! |
Please use v1.1.0 which has been just released. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi all,
The SFN
CreateStateMachine
API call has a "type" parameter for explicitly tagging a state machine as either standard or express:https://docs.aws.amazon.com/step-functions/latest/apireference/API_CreateStateMachine.html
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/stepfunctions.html#SFN.Client.create_state_machine
As far as I can tell, however, this Terraform module doesn't offer any way to specify the "type" of a state machine.
Are there any plans to add support for the "type" parameter? Or is this already possible today, and if so, how?
Our team is thinking of using a mix of standard and express state machines, so it would be useful to have the ability to customize this.
Thanks!
The text was updated successfully, but these errors were encountered: