-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
fix(nextjs-component, nextjs-cdk-construct): create AWS resources for dynamic SSG (#1476) #1477
Conversation
Handler Size Report
Base Handler Sizes (kB) (commit bdef74d){
"Lambda@Edge": {
"Default Lambda": {
"Standard": 1227,
"Minified": 433
},
"API Lambda": {
"Standard": 86,
"Minified": 34
},
"Image Lambda": {
"Standard": 894,
"Minified": 354
},
"Regeneration Lambda": {
"Standard": 620,
"Minified": 220
}
}
} New Handler Sizes (kB) (commit a28ec93){
"Lambda@Edge": {
"Default Lambda": {
"Standard": 1227,
"Minified": 433
},
"API Lambda": {
"Standard": 86,
"Minified": 34
},
"Image Lambda": {
"Standard": 894,
"Minified": 354
},
"Regeneration Lambda": {
"Standard": 620,
"Minified": 220
}
}
} |
Codecov Report
@@ Coverage Diff @@
## master #1477 +/- ##
==========================================
- Coverage 84.15% 84.14% -0.02%
==========================================
Files 96 97 +1
Lines 3371 3381 +10
Branches 1006 1009 +3
==========================================
+ Hits 2837 2845 +8
- Misses 474 476 +2
Partials 60 60
Continue to review full report at Codecov.
|
Looks fine to me, though please fix the style issue as reported by codacy. Also can you check if it is needed in the CDK deployer as well? (can be in another PR if needed) |
@dphang thanks you. I updated the commit. I also fixed the nextjs-cdk-construct. actually it reads to different manifest, the conditions also change. As below
|
Thanks, though it looks like the build is still failing from cdk-construct due to typing issue.. |
Now I saw it merged. Thanks |
it adds the resource creation conditions that my suggestions for fix #1476. I think we need to create SQS and Regeneration Handler at deployment time, because it can 'fallback: true|blocking' with 'revaliate'.
I would like your review on whether that is an appropriate solution or not. thanks