update TDA version #367
Merged
update TDA version #367
Conversation
This file contains hidden or 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
Why these changes are being introduced: We formerly documented and used the tag ':latest' for standing up a local Opensearch instance, but this has the potential to pull a newer version than we currently have in AWS. How this addresses that need: * Pins references in README and Docker Compose YAML to version 2 * Will require updates when we eventually migrate to version 3 Side effects of this change: * Build Opensearch 2.x locally for testing and development Relevant ticket(s): * None
Pull Request Test Coverage Report for Build 17494822697Details
💛 - Coveralls |
jonavellecuerdo
approved these changes
Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Purpose and background context
The primary purpose of this PR is to update the TDA version to
3.2, picking up new read methods.Additionally, this updates
READMEand the Docker Compose YAML to pin to Opensearch version2.xto align with our current version in AWS.How can a reviewer manually see the effects of these changes?
Successful StepFunction run in Dev shows pipeline lambdas using updated TDA version: https://222053980223-fpdparvm.us-east-1.console.aws.amazon.com/states/home?region=us-east-1#/v2/executions/details/arn:aws:states:us-east-1:222053980223:execution:timdex-ingest-dev:ea132241-1c30-4992-9b59-c5ba15a40ab9.
Includes new or updated dependencies?
YES
Changes expectations for external applications?
NO
What are the relevant tickets?