fix(s3-deployment): custom resource fails to run aws-cli (#3668)

* fix(s3-deployment): custom resource fails to run aws-cli Due to a change in our build environment (superchain) to Amazon Linux, the structure of the python modules installed in the s3 deployment custom resource lambda handler changed and the "yaml" module ended up under `lib64` instead of `lib`. Also, upgrade awscli to 1.16.218 and boto3 to 1.9.208 Fixes #3656 * do not attempt to move files from lib64 if they dont exist
aws · Aug 15, 2019 · 6eabe6d · 6eabe6d
1 parent 9e46532
commit 6eabe6d
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/packages/@aws-cdk/aws-s3-deployment/lambda/build.sh b/packages/@aws-cdk/aws-s3-deployment/lambda/build.sh
@@ -29,6 +29,9 @@ cd ${staging}
 # platforms that have a default --prefix set.
 pip3 install --ignore-installed --prefix ${piptemp} -r ${staging}/requirements.txt
 mv ${piptemp}/lib/python*/*-packages/* .
+[ -d ${piptemp}/lib64 ] && mv ${piptemp}/lib64/python*/*-packages/* .
+rm -fr ./awscli/examples
+
 
 # create archive
 zip -qr ${bundle_out} .

diff --git a/packages/@aws-cdk/aws-s3-deployment/lambda/src/requirements.txt b/packages/@aws-cdk/aws-s3-deployment/lambda/src/requirements.txt
@@ -1,2 +1,2 @@
-awscli==1.16.34
-boto3==1.9.177
+awscli==1.16.218
+boto3==1.9.208