[plugin] Use LAMBDA_USE_LOCAL_DEPS env var in local builds with docker #325
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the newly introduced
LAMBDA_USE_LOCAL_DEPS
environment variable inside Docker to allow to build Swift Lambda function using the local copy of the runtimeMotivation:
When developing and testing ideas on the Swift AWS Lambda Runtime, we often need to build code for deployment.
The local and CI build systems have been modified to allow to reference the local filesystem version of the library, instead of the remote one on Git. It uses the
LAMBDA_USE_LOCAL_DEPS
to make the difference. The examples'Package.swift
have been updated by #292Modifications:
This PR, adds a check in the archiver plugin to mount
../..
in the docker container rather than.
when building with local dependencies. This allows to refer to the local copy of the Swift AWS Lambda runtime library from within docker.Result: