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
|`BUILD_INDIVIDUALLY`| Whether to build each executable individually, either via `--bin` or `--package`. |
296
-
|`DEFAULT_LOG_LEVEL`| Log Level for non-module libraries. Note that this value is only used when `RustFunctionProps.setupLogging` is enabled. Defaults to `warn`. |
297
-
|`MODULE_LOG_LEVEL`| Log Level for a module (i.e. the executable). Note that this value is only used when `RustFunctionProps.setupLogging` is enabled. Defaults to `debug`. |
298
-
|`WORKSPACE_DIR`| Sets the root workspace directory. By default, the workspace directory is assumed to be the directory where `cdk` was invoked.<br><br>This directory should contain at the minimum a `Cargo.toml` file which defines the workspace members. |
299
-
|`FEATURES`| A list of features to activate when compiling Rust code. These must also be added to the `Cargo.toml` file. |
300
-
|`BUILD_ENVIRONMENT`| Key-value pairs that are passed in at compile time, i.e. to `cargo build` or `cargo lambda`. This differs from `environment`, which determines the environment variables which are set on the AWS Lambda functionitself.|
301
-
|`EXTRA_BUILD_ARGS`| Additional arguments that are passed in at build time to both `cargo lambda`. For example, [`--all-features`]. |
302
-
|`SKIP_BUILD`| Whether to skip building Rust Lambdas -- e.g. skip the compile step with `cargo lambda`.<br><br>Alternatively, this can be setin the `build` context, when invoking `cdk` -- for example:<br>`$ cdk synth -c build=[T \|true\|1\| Y \| yes \| ok \| on]`<br>Any values other than the listed evaluate to `false`. So, this would skip the build step on `synth`:<br>`$ cdk synth -c build=0`|
|`BUILD_INDIVIDUALLY`| Whether to build each executable individually, either via `--bin` or `--package`. |
296
+
|`DEFAULT_LOG_LEVEL`| Log Level for non-module libraries. Note that this value is only used when `RustFunctionProps.setupLogging` is enabled. Defaults to `warn`. |
297
+
|`MODULE_LOG_LEVEL`| Log Level for a module (i.e. the executable). Note that this value is only used when `RustFunctionProps.setupLogging` is enabled. Defaults to `debug`. |
298
+
|`WORKSPACE_DIR`| Sets the root workspace directory. By default, the workspace directory is assumed to be the directory where `cdk` was invoked.<br><br>This directory should contain at the minimum a `Cargo.toml` file which defines the workspace members. |
299
+
|`FEATURES`| A list of features to activate when compiling Rust code. These must also be added to the `Cargo.toml` file. |
300
+
|`BUILD_ENVIRONMENT`| Key-value pairs that are passed in at compile time, i.e. to `cargo build` or `cargo lambda`. This differs from `environment`, which determines the environment variables which are set on the AWS Lambda functionitself.|
301
+
|`EXTRA_BUILD_ARGS`| Additional arguments that are passed in at build time to both `cargo lambda`. For example, [`--all-features`]. |
302
+
|`SKIP_BUILD`| Whether to skip building Rust Lambdas -- e.g. skip the compile step with `cargo lambda`.<br><br>Alternatively, this can be setin the `build` context, when invoking `cdk` -- for example:<br>`$ cdk synth -c build=[T \|true\| 1 \| Y \| yes \| ok \| on]`<br>Any values other than the listed evaluate to `false`. So, this would skip the build step on `synth`:<br>`$ cdk synth -c build=0`|
0 commit comments