Keep bootstrap executable after creating the release zipfile

This is convenient for local testing because one can skip the
unzipping step before using the `lambci/lambda` image.

Author: medwards

README.md

@@ -79,13 +79,10 @@ You can invoke this bootstap executable with the lambda-ci docker image for the
 ```sh
 # start a one-off docker container replicating the "provided" lambda runtime
 # awaiting an event to be provided via stdin
-$ unzip -o \
-    target/lambda/release/{your-binary-name}.zip \
-    -d /tmp/lambda && \
-  docker run \
+$ docker run \
     -i -e DOCKER_LAMBDA_USE_STDIN=1 \
     --rm \
-    -v /tmp/lambda:/var/task:ro,delegated \
+    -v ${PWD}/target/lambda/release:/var/task:ro,delegated \
     lambci/lambda:provided
 
 # provide an event payload via stdin (typically a json blob)

build.sh

@@ -49,20 +49,18 @@ export CARGO_TARGET_DIR=$PWD/target/lambda
 
 function package() {
     file="$1"
+    OUTPUT_FOLDER="output"
     if [[ "${PROFILE}" == "release" ]] && [[ -z "${DEBUGINFO}" ]]; then
         objcopy --only-keep-debug "$file" "$file.debug"
         objcopy --strip-debug --strip-unneeded "$file"
         objcopy --add-gnu-debuglink="$file.debug" "$file"
     fi
     rm "$file.zip" > 2&>/dev/null || true
-    # note: would use printf "@ $(basename $file)\n@=bootstrap" | zipnote -w "$file.zip"
-    # if not for https://bugs.launchpad.net/ubuntu/+source/zip/+bug/519611
-    if [ "$file" != ./bootstrap ] && [ "$file" != bootstrap ]; then
-        mv "${file}" bootstrap
-        mv "${file}.debug" bootstrap.debug > 2&>/dev/null || true
-    fi
-    zip "$file.zip" bootstrap
-    rm bootstrap
+    rm -r "${OUTPUT_FOLDER}" > 2&>/dev/null || true
+    mkdir "${OUTPUT_FOLDER}"
+    cp "${file}" "${OUTPUT_FOLDER}/bootstrap"
+    cp "${file}.debug" "${OUTPUT_FOLDER}/bootstrap.debug" > 2&>/dev/null || true
+    zip -j "$file.zip" "${OUTPUT_FOLDER}/bootstrap"
 
     if test -f "$HOOKS_DIR/$PACKAGE_HOOK"; then
         echo "Running package hook"