-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Enhancement: Step Functions for Express Workflows #12249
Enhancement: Step Functions for Express Workflows #12249
Conversation
Updated by resolving conflict. |
@VVolotivskyi Bump. When is it possible to get this merged and out? |
0ca9b6f
to
19c70b0
Compare
@bflad - Is there any chance this can be reviewed within the next week or two? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with some minuscule polish suggestions to get the ball rolling @grahamjenson @bflad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any chance that this can be merged?
@benmcmeen I hope we can get this merged. most of my time is spent just fixing conflicts. |
Co-authored-by: Dexter Miguel <me@dextermiguel.com>
Co-authored-by: Dexter Miguel <me@dextermiguel.com>
Co-authored-by: Dexter Miguel <me@dextermiguel.com>
59913fe
to
5f3f198
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great if this could get merged.
It would be great if this could get merged. |
So - do any of the maintainers ever review PRs on this project? This has been out there forever and contains useful features. It's radio silent on this feature and doesn't exactly inspire confidence about future enhancements or break/fix. |
633 open pull requests show why we shouldn’t put our faith in terraform over cdk. This will never be merged. |
Get more people to vote :) |
Plenty of people have voted BOTH times this PR has been submitted. It's not a community participation issue. It's a maintenance shortcoming. |
@bflad When can we expect this? Because type can't be changed once state is created, I consider this to be critical. I don't see any workarounds except for this PR right now. |
@breathingdust @anGie44 Can you help in merging this PR? |
Hi all! 👋 Just a quick update to say we are tracking this for attention in the near future, but at this time we can't give you an ETA. We appreciate your patience and hope to get back to you with an update soon. |
Bump, any chance we can get some movement on this? No activity in over 2 months... |
I gave up on this one a loooooong time ago. The SFN module in TF doesn't support XRay tracing, logging config, and all kinds of other things I also couldn't wait for. I ended up just managing this with a script and direct CLI call. |
This feature was included in the previous roadmap (November 2020 - January 2021), but apparently didn't make it. Now the issue is not mentioned in the current Roadmap nor the upcoming release (3.27.0). What's happening? |
Agreed w/ @SebRamsland |
Sorry for the confusion on the roadmap everyone. This is being merged and will be released in v3.27.0. |
This has been released in version 3.27.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Improved from #11570
This adds support for AWS Step Functions for Express Workflows, that are ideal for high-volume, event-processing workloads such as IoT data ingestion, streaming data processing and transformation, and mobile application backends. They can run for up to five minutes. Execution history is optionally available in Amazon CloudWatch Logs. Express Workflows employ an at-least-once model, where there is a possibility that an execution might be run more than once. This makes them ideal for orchestrating idempotent actions such as transforming input data and storing via PUT in Amazon DynamoDB. Express Workflow executions are billed by the number of executions, the duration of execution, and the memory consumed.
Changes proposed in this pull request:
resource_aws_sfn_state_machine.go: Add type and logging_configuration arguments
resource_aws_sfn_state_machine_test.go: Extend acceptance tests
sfn_state_machine.html.markdown: Extend documentation
Community Note
Relates OR Closes #11348 #11374 #12192 #11570
Release note for CHANGELOG:
Output from acceptance testing: