profile
viewpoint
Matt Morgan elthrasher Hobsons Arlington, VA

TrainingByPackt/TypeScript 1

Take a practical approach to learning TypeScript from the ground up, starting with the fundamentals all the way through to building real world applications.

elthrasher/awesome-cdk 0

A collection of awesome things related to the AWS Cloud Development Kit (CDK)

elthrasher/aws-cdk 0

The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

push eventPacktWorkshops/The-TypeScript-Workshop

elthrasher

commit sha 53c7ac336e8bdc96b2aa4003a3761ee0faaa0ab3

chapter 3 exercises refactoring

view details

push time in a month

create barnchelthrasher/mocking-aws-with-jest

branch : main

created branch time in 2 months

created repositoryelthrasher/mocking-aws-with-jest

created time in 2 months

push eventelthrasher/cdk-apigateway-dynamodb

elthrasher

commit sha 78430d3fbdcdb50edccd39f73f3e90fd21c7de63

deps

view details

push time in 2 months

push eventTrainingByPackt/TypeScript

elthrasher

commit sha 7bcd44ee4eb23e09c85dd8b2566dfe2edec3687c

deps

view details

push time in 2 months

push eventTrainingByPackt/TypeScript

elthrasher

commit sha a0601d7786be53ddda59d68e89a227f713ae6cb8

chapter 3 deps

view details

push time in 2 months

push eventTrainingByPackt/TypeScript

Matt Morgan

commit sha db50b10b8ac1a875770f53955caba9c7945f421d

Update README.md

view details

push time in 2 months

push eventelthrasher/cdk-step-functions-example

elthrasher

commit sha 4f289132e43f33ef287d31efecc9055dede45a77

deps

view details

push time in 3 months

push eventelthrasher/cdk-dynamo-lambda-loader

elthrasher

commit sha cbd2ef8b0e5994d490e1abe9bb048c2f7aa125ac

deps

view details

push time in 3 months

push eventelthrasher/cdk-dynamo-custom-loader

elthrasher

commit sha 2a4467dbeda634455e4f01c27b0f7aa0f397096f

deps

view details

push time in 3 months

issue commentelthrasher/http-lambda-invoker

Request body is getting base64 encoded

Thanks guys. I appreciate the feedback. My team isn't actually using this yet, so you guys are saving us some future churn. 👍

mcintyre94

comment created time in 3 months

pull request commentelthrasher/sam-typescript-webpack-sample

Bump winston from 3.2.1 to 3.3.3

@dependabot rebase

dependabot-preview[bot]

comment created time in 3 months

push eventelthrasher/sam-typescript-webpack-sample

elthrasher

commit sha 18c8b8bff16230b5b28039e7884ef141094445c3

deps

view details

push time in 3 months

issue closedelthrasher/sam-typescript-webpack-sample

Question about bundling

Thank you very much, your code helped a lot! I've got a couple of questions and was hoping you may help out please:

  1. Do you confirm that each lambda function will only be bundled with the dependencies that it imports, and not all the dependencies in the main package.json file?
  2. Is there any way to prune the dependencies to not include redundant code there-within as well? I imported Stripe and noticed that there are irrelevant lines in there, that made it into the final JavaScript file.

Thanks again!

closed time in 3 months

picosam

issue commentelthrasher/sam-typescript-webpack-sample

Question about bundling

Closing due to inactivity.

picosam

comment created time in 3 months

issue commentelthrasher/http-lambda-invoker

Request body is getting base64 encoded

Since it's technically a breaking change, I posted the fix to docker pull elthrasher/http-lambda-invoker:release-0.1.0 and it's in latest as well. Please let me know if that works.

mcintyre94

comment created time in 3 months

created tagelthrasher/http-lambda-invoker

tag0.1.0

created time in 3 months

release elthrasher/http-lambda-invoker

0.1.0

released time in 3 months

push eventelthrasher/http-lambda-invoker

elthrasher

commit sha c7c3c2678c012b204760a755b3295d70ac049f16

go version

view details

push time in 3 months

push eventelthrasher/http-lambda-invoker

elthrasher

commit sha cae0c7c2d81883b42f6a30b687db844b315c1d9e

handle body encoding

view details

push time in 3 months

issue commentelthrasher/http-lambda-invoker

Request body is getting base64 encoded

Okay, I've tagged the current head: docker pull elthrasher/http-lambda-invoker:release-0.0.1

I'll release the fix today or tomorrow. Just want to figure out if I can have better unit tests (still learning go).

mcintyre94

comment created time in 3 months

created tagelthrasher/http-lambda-invoker

tag0.0.1

created time in 3 months

release elthrasher/http-lambda-invoker

0.0.1

released time in 3 months

issue commentelthrasher/http-lambda-invoker

Request body is getting base64 encoded

Okay, this was pretty simple to fix and you can chalk it up to my inexperience with golang.

@S-Cardenas and @mcintyre94 are you using the above hack right now? If I just release the fix, I assume that would break some process you have. I guess I should add image tagging instead of stamping everything with latest.

mcintyre94

comment created time in 3 months

issue commentaws/aws-cdk

[aws-lambda-nodejs] a single lambda creation takes 30s every time

@vvo Thanks, I saw that, but I'm using TypeScript. Would be glad to give it a try and give you feedback after you introduce support for TypeScript.

vvo

comment created time in 3 months

issue commentelthrasher/http-lambda-invoker

queryStringParameters getting mangled

@jdobyns So sorry for not getting back to you. I honestly didn't know that I don't automatically get notified of new issues. Have you come up with any solution or workaround? I can give this a look if not.

jdobyns

comment created time in 3 months

issue commentelthrasher/http-lambda-invoker

Request body is getting base64 encoded

@mcintyre94 So sorry for not getting back to you. TIL after a decade with github that I don't automatically get notifications on issues. :(

I'll see if I can use a different type there. I agree that seems weird.

mcintyre94

comment created time in 3 months

pull request commentelthrasher/cdk-apigateway-dynamodb

Bump @types/jest from 26.0.5 to 26.0.7

@dependabot rebase

dependabot-preview[bot]

comment created time in 3 months

issue commentaws/aws-cdk

[aws-lambda-nodejs] a single lambda creation takes 30s every time

First the requested info... https://github.com/jogold/cdk-lambda-nodejs-monorepo yarn cdk synth 3.85s user 0.82s system 9% cpu 48.052 total https://github.com/jogold/cdk-s3-thumbnail npm run cdk synth 4.77s user 0.75s system 12% cpu 44.762 total

This one is the project I'm working on right now: npx cdk synth 4.30s user 0.48s system 7% cpu 1:00.98 total

And here's one of my sample projects: https://github.com/elthrasher/cdk-step-functions-example npx cdk synth 5.09s user 0.94s system 3% cpu 2:39.58 total

A minute is a long time to wait - especially since I must synth to run unit tests. The numbers above are after running several times, so Docker layers should be cached as well as possible.

  1. I get the reasons for building with Docker, but building the functions one at a time as opposed to being able to have a single parcel/webpack/whatever build with multiple entrypoints isn't going to scale real well. My project has five functions, which is why it takes more than two minutes. I tried to figure out CDK_DOCKER, but it seems like I have to provide a docker-compatible API? It would be great if I could just bail out of the whole thing and agree to supply my own parcel (or webpack, which is more complex, but also more mature) build.
  2. I tried putting my stack into my build system, which is Docker-based and it's nearly impossible to get it to work. I must share my docker.sock (which is fine), but doing that means the volume share will go back to the HOST, not the container I'm trying to build in, so paths get crazy since this module attempts to take the path from the container, not host, but the volume will be shared to the host! (see also: https://serverfault.com/a/819371) For this reason, I basically flat out can't use this module without switching to another build system.
  3. Even though it looks like I need a non-Docker option, if I were to build in Docker, I'd really try to figure out a way to COPY the source into the initial build, then just share the output (perhaps via docker cp). That would give me the advantage of Docker caching on the build, which is a great thing to have. Very often my team has made a change to the stack that has nothing to do with the functions, yet we must always wait for the functions to build from scratch every time.

I'm at the point where I either have to do a two-step build (build with webpack, then use lambda.Function) or come up with my own construct, but I thought I'd see where you guys were. I can contribute here or go my own way (or maybe there's some sorcery with CDK_DOCKER you can point me to).

Thanks for listening :)

vvo

comment created time in 3 months

push eventelthrasher/sam-typescript-webpack-sample

elthrasher

commit sha 19f60ad0f7dba2799367e021dc6e439a061619eb

dynamic entries

view details

push time in 3 months

push eventTrainingByPackt/TypeScript

elthrasher

commit sha 2d389e81ed8ea0e64f494e1bf2cf9188601b265d

Activity15.01

view details

push time in 3 months

push eventTrainingByPackt/TypeScript

elthrasher

commit sha 248ae4f1620aba057d38c26f42928e2c02aa18b5

Exercise15.03

view details

push time in 3 months

more