feat(reportextractor): GuCDK defined lambda - #1616
Merged
Merged
Conversation
Contributor
Contributor
Contributor
Contributor
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 13, 2026 14:04
82b4fc3 to
d809d01
Compare
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 13, 2026 14:19
ce2911b to
7d64dae
Compare
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 13, 2026 15:22
7d64dae to
8121be2
Compare
akash1810
added a commit
that referenced
this pull request
Jan 14, 2026
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/reportextractor-cdk
branch
from
January 14, 2026 09:26
8121be2 to
4df30d0
Compare
akash1810
added a commit
that referenced
this pull request
Jan 14, 2026
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
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 14, 2026 12:32
535c596 to
7343102
Compare
Defining the reportextractor lambda in GuCDK. This definition is in parallel to the one in `reportextractor/cfn.yaml`.
Match the additional permissions in the YAML that are not provided by default from GuCDK.
Riff-Raff's tag based lambda discovery expects to find one lambda. Currently, the YAML and GuCDK lambdas have the same tags, therefore we have to configure `riff-raff.yaml` with `functionNames` and explicitly name the GuCDK lambda.
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 14, 2026 14:20
7343102 to
f26ffd2
Compare
To prevent the YAML and GuCDK lambda from running at the same time, and over-writing each other's output, disable the schedule for the YAML lambda.
akash1810
force-pushed
the
aa/reportextractor-cdk
branch
from
January 14, 2026 14:28
9551b12 to
62bf839
Compare
akash1810
marked this pull request as ready for review
January 14, 2026 14:56
akash1810
added a commit
that referenced
this pull request
Jan 14, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
2 tasks
jorgeazevedo
approved these changes
Jan 14, 2026
akash1810
added a commit
that referenced
this pull request
Jan 15, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
akash1810
added a commit
that referenced
this pull request
Jan 16, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
akash1810
added a commit
that referenced
this pull request
Jan 19, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
akash1810
added a commit
that referenced
this pull request
Jan 20, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
akash1810
added a commit
that referenced
this pull request
Jan 22, 2026
Since #1616, this lambda is defined in GuCDK. Note, this change doesn't delete the CloudFormation stack, we'd need to do this manually.
This was referenced Jan 30, 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
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.
Note
Easiest to review commit by commit.
What does this change?
Follows #1612, adding a GuCDK defined version of the
reportextractorlambda to thereportCFN stack. That is, this change yields the following CFN stacks and resources:reportwithreportEC2 app andreportextractorlambdareportextractorwithreportextractorlambda1The GuCDK version isn't an exact replica of the YAML defined one. Most notably the custom CloudWatch Logs policy is not replicated as it isn't necessary; lambdas implicitly have permissions to write to CloudWatch Logs via AWSLambdaBasicExecutionRole and the application code does not produce CloudWatch Metrics.
How to test
Deploy this branch
Invoke the legacy YAML defined lambda (logs)
Calculate the SHA-256 of the
notifications.jsonoutput fileInvoke the GuCDK defined lambda (logs)
Calculate the SHA-256 of the
notifications.jsonoutput file and compare it to step 3, it should match.Footnotes
A follow-up PR to remove the
reportextractorCFN stack will be made after this PR. ↩