Batcher Lambda, infrastructure and build #2728
Merged
+186
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 9, 2024
kenoir
force-pushed
the
rk/lambda-batcher-build
branch
from
18dda3a
to
5678429
Compare
| event: JavaMap[String, String], | ||
| context: Context | ||
| ): String = { | ||
| info(s"running batcher lambda, got event: $event") |
kenoir
force-pushed
the
rk/lambda-batcher-build
branch
from
3e7265b
to
1726946
Compare
paul-butcher
approved these changes
Oct 15, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Part of #2721
Introduce lambda infrastructure for batcher service and start setup build process.
This change does not include code changes to allow the batcher to run as a Lambda other than a skeleton class and handler function.
Depends: wellcomecollection/terraform-aws-ecs-service#53
Next (in a new PR): Add queue & lambda trigger functionality
How to test
How can we measure success?
When code changes are ready from #2721, they can be easily deployed.
Have we considered potential risks?
We should avoid disrupting the existing infra, build & deploy and create a parallel lambda implementation to mitigate risk involved with breaking the existing process.