feat(core): local bundling provider

[jogold]

The local bundling provider implements a method tryBundle() which should
return true if local bundling was performed. If false is returned, docker
bundling will be done.

This allows to improve bundling performance when the required dependencies are
available locally.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[jogold]

@eladb let's first discuss the concept... currently works with aws-lambda-nodejs.

[jogold]

Bundling is currently documented here: https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-s3-assets/README.md#asset-bundling

Should I add the doc about local bundling there? Move everything to core?

Pull request has been modified.

[jogold]

newly required property 'docker' used to be missing... breaking change in aws-lambda and core, should we just add local and not nest the existing props inside docker?

[eladb]

newly required property 'docker' used to be missing... breaking change in aws-lambda and core, should we just add local and not nest the existing props inside docker?

Yes I figured. Let's just keep the current api (without the docker indirection) and add local. Just make sure docstrings for all existing properties indicate that these are for the docker execution.

[eladb]

Minor

[jogold]

@eladb will leave this in Draft while I test that I can implement local bundling correctly in aws-lambda-nodejs.

[eladb]

Should be tryBundle no?

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: 398e8e2
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).