-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Minor: Implementation of the aws_lambda_event_source_mapping
resource to easily set a stream or a queue as trigger for lambda.
#75
base: main
Are you sure you want to change the base?
Conversation
/terratest |
/terratest |
/terratest |
Hi @milldr I think I've fixed the terraform/tofu testing passing a few fake parameters, let me know if that's OK and we're ready for another go :) |
/terratest |
Cloudposse Dynamo DB table module added to examples |
/terratest |
/terratest |
💥 This pull request now has conflicts. Could you fix it @nnsense? 🙏 |
Hey @milldr, if you have time, could you review again? I hope I've fixed everything, sorry for the delay.. busy days! Thanks :) |
/terratest |
Fixed (hopefully), overlloked those dots 🤦🏻♂️ |
/terratest |
what
Implementation of the
aws_lambda_event_source_mapping
resource, allowing to set a Kinesis stream, DynamoDB stream, or SQS queue as a trigger for lambda. I've purposely kept things simple allowing only a few variables:source_mapping_arn
pointing to thearn
of the triggering resource (eg, the lambda execution role)source_mapping_batch_size
allowing to tune the number of events we pass to the function.source_mapping_starting_position
, because it's usually required and terraform complains if it's unsetsource_mapping_starting_position_timestamp
, if someone wants to useAT_TIMESTAMP
in Kinesis.why
It's useful to get lambda triggered by other resources without having to set just one resource in another module.