-
Notifications
You must be signed in to change notification settings - Fork 4k
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
StepFunction Service Integration with DynamoDb #5782
Comments
Hi @sacag thanks for reporting this bug. In order to understand the issue better could you give us a full description of the issue you're encountering. You can just edit your initial post and add a description under the first section. Thanks! |
@SomayaB - Sorry, missed the bug description. Should be there now. Basically, there doesn't seem to be a way to access the dynamodb api from step functions in C# CDK. Although, the documentation says otherwise. |
@SomayaB - Any update on this issue? |
Thanks for adding a description @sacag! We're looking into this and will update this issue when there is movement. |
You are right that there are no pre-built constructs that expose this functionality right now. You can implement it yourself by implementing |
@rix0rrr - As of now we are creating a lambda function which interacts with the dynamodb and passes on the result to next task. Is there a timeline when a pre-built construct for this will be available for .NET? |
Looks like it. Thanks for fishing this out. Resolving, @ayush987goyal has implemented this and will be available in the next CDK release. |
Description
Seems like the service integration between step function and dynamodb api is missing? Or is it lack of documentation? See the below code snippet which works for publishing to SNS from step-function task. Cannot find anything to do the same for dynamodb.
Reproduction Steps
Cannot find a similar way to interact with Dynamodb in the step function task as you can see above for SNS (PublishToTopic).
Error Log
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: