This message was deleted.

i currently package up my layers via a bash script. Here's and example stub that you might find useful

for l in "${FOR_LAYERS[@]}"; do
  REQUIREMENTS_FILE=${PWD%/*}/source/services/$l/requirements.txt
  if [ -f $REQUIREMENTS_FILE ] && [ ! -f layers/$l-layer.zip ]; then
    docker run -v "$PWD":/var/task -v $REQUIREMENTS_FILE:/var/requirements.txt "lambci/lambda:build-python3.8" /bin/sh -c "pip install -r /var/requirements.txt -t python/lib/python3.8/site-packages/; exit"
    zip -r layers/$l-layer.zip python
    docker run -v "$PWD":/var/task "lambci/lambda:build-python3.8" /bin/sh -c "rm -rf python/"
  fi
done

layers huh...i was reading that you can do a /.packages folder maybe?

you could do that, can update the above stub to include the code source files as well as setting up the dependencies. I package layers separately as often there are a bunch of common dependencies across our various serives so the layer is then reused. I no longer provide a zip to pulumi to upload for the lambda itself and just point the config to the source directory (pulumi then zips it up as part of pulumi up)

makes sense

yeah when creating the resource its passed into the

code

argument

code=pulumi.AssetArchive({
        '.': pulumi.FileArchive('build/lambdas/api-webhooks-lambda.zip')
    })

right i mean if I install packages to a packages folder apparently they have to be at the root

if you are splitting them out then i think the only way you can do that with pulumi will be to use layers

she aint pretty but I think it will work inside docker image to spit out this zip

pip install --target ./packages -r requirements.txt && zip -r linkgen.zip ./ -x "packages/*" "tests/*" "*.DS_Store" && cd packages/ && zip -ur ../linkgen.zip ./

👏