-
Notifications
You must be signed in to change notification settings - Fork 3
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
Automated sync example #38
base: main
Are you sure you want to change the base?
Conversation
…173f037babe6d71eb9f4db214e2c9a14248c43dae.plan.json
…173f037babe6d71eb9f4db214e2c9a14248c43dae.zip
…7f7ebca5d3b5a59c4a1e2d0988b15f1319feb2836.zip
/do-e2e-tests |
End to end test has been scheduled |
E2E tests in progress |
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.
E2E tests completed successfully
|
||
handler = "app.lambda_handler" | ||
runtime = "python3.12" | ||
architectures = ["arm64"] |
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.
Consider leaving out the optional architectures
or alternatively a variable:
variable "lambda_architecture" {
type = string
description = "The lambda runtime architecture"
nullable = false
default = "arm64"
validation {
condition = contains(["x86_64", "arm64"], var.architecture)
error_message = "The architecture must be either 'x86_64' or 'arm64'."
}
}
This PR provides an example of how to schedule document ingestion from S3. It uses the S3 to SQS event integration to get a count of changes. There is also an EventBridge schedule that can ensure there is a maximum latency for the ingestion of source documents.