You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ You can pass additional flags to `cargo`, the Rust build tool, by setting the `C
34
34
35
35
Unzipped `boostrap` and `boostrap.debug` files are always available
36
36
under `target/lambda/${PROFILE}/output/${BIN}` dir. If you want only them and don't
37
-
need a `.zip` archive (e.g. for when running lambdas locally) pass `-e SKIP_ZIPPING=1`
37
+
need a `.zip` archive (e.g. for when running lambdas locally) pass `-e PACKAGE=false`
38
38
flag. More on that in [local testing](#-local-testing).
39
39
40
40
A typical docker run might look like the following.
@@ -91,18 +91,18 @@ Once you've built a Rust lambda function artifact, the `provided` runtime expect
91
91
deployments of that artifact to be named "**bootstrap**". The `lambda-rust` docker image
92
92
builds a zip file, named after the binary, containing your binary file renamed to "bootstrap" for you, but zip file creation is unnecessary for local development.
93
93
94
-
In order to prevent the creation of an intermediate `.zip` artifact when testing your lambdas locally, pass `-e SKIP_ZIPPING=1` during the build. After that the necessary
94
+
In order to prevent the creation of an intermediate `.zip` artifact when testing your lambdas locally, pass `-e PACKAGE=false` during the build. After that the necessary
95
95
output (not zipped) is available under `target/lambda/{profile}/output/{your-lambda-binary-name}` dir.
96
96
You will see both `bootstrap` and `bootstrap.debug` files there.
97
-
> **⚠️ Note:**`SKIP_ZIPPING=1` prevents `package` hook from running.
97
+
> **⚠️ Note:**`PACKAGE=false` prevents `package` hook from running.
98
98
99
99
You can then invoke this bootstap executable with the lambda-ci docker image for the `provided` AWS lambda runtime with a one off container.
100
100
101
101
```sh
102
102
# Build your function skipping the zip creation step
103
103
# You may pass `-e PROFILE=dev` to build using dev profile, but here we use `release`
0 commit comments