feat(reportextractor): Mark YAML defined infrastructure as "legacy" - #1617
Merged
Conversation
Contributor
akash1810
marked this pull request as ready for review
January 14, 2026 10:59
In #1616 we're defining the lambda in GuCDK. We'll have to configure Riff-Raff to discover the new lambda via a name tag discovery fails when multiple lambdas are matched. To support this, rename the YAML lambda with the "legacy" prefix so that the GuCDK lambda can be named "mobile-notifications-reportextractor-(CODE|PROD)".
akash1810
force-pushed
the
aa/legacy-reportextractor
branch
from
January 14, 2026 12:32
4413239 to
fdd96c5
Compare
aracho1
approved these changes
Jan 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What does this change?
In #1616 we're defining the lambda in GuCDK and will dual-stack its deployment. This change renames the YAML defined lambda to
legacy-mobile-notifications-reportextractor-(CODE|PROD)to make it easier to distinguish it from the GuCDK lambda.How to test
Deploy this branch
Invoke the lambda:
Locate the logs in Central ELK, they should have a
cloudwatchLogGroupmarker value of/aws/lambda/legacy-mobile-notifications-reportextractor-CODE. Using devx-logs:devx-logs --space mobile \ --filter cloudwatchLogGroup="/aws/lambda/legacy-mobile-notifications-reportextractor-CODE" \ --column message \ --column cloudwatchLogGroup