Aws-sam-cli

What's new?
You can now use the `sam build` command to compile deployment packages for AWS Lambda functions written in supported Node.js runtimes. Huge shout-out to gojko for this contribution!

You can now debug Lambda functions written in .NET Core using Visual Studio Code. To get started, check out the documentation: [Debugging .NET Core functions](https://github.com/awslabs/aws-sam-cli/blob/develop/docs/usage.rst#debugging-net-core-21--20-functions). Huge shout-out to ndobryanskyy for this contribution!

Changelog
docs: Update Slack invite link (781)
fix: Create Layer Cache during building image (823)
docs: list Ruby2.5, Python3.7 and Provided as supported runtime (822)
fix: Making hello world java sample more idiomatic (802)
fix: Update to .NET Core init template (705)
fix: Stop html encoding of options for generate-event (824)
docs: Issue templates for bug and feature requests (726)
fix: Fix Makefile typo (829)
Feature: .NET Core 2.0/2.1 debugging support (825)
refactor: Move checking Docker connectivity to ContainerManager (828)
fix: Update functional tests to work (841)
Feature: Support building Node.js functions (845)

What's New
Lambda functions in a serverless application typically share common dependencies such as SDKs, frameworks, and runtimes. Lambda Layers are a new type of artifact that can contain arbitrary code and data, and may be referenced by multiple functions at the same time. With layers, you can centrally manage common components across multiple functions enabling better code reuse. You can now use AWS SAM and AWS SAM CLI to locally test, deploy and manage serverless applications that leverage Layers.

When you invoke a function (AWS::Lambda::Function or AWS::Serverless::Function) that uses Layers, SAM CLI downloads the layer and makes it available in the container for your function code to use.

Changelog:
fix: AWS CLI on windows can be called aws.cmd or aws.exe (786)
fix: typo in development guide doc (791)
fix: astroid version (795)
fix: Allow local paths for AWS::Lambda::Function (808)
chore: Update aws-lambda-builders (808)
feat: Support Python3.7, Ruby2.5, and Provided Runtimes (808)
feat: Support local testing and debugging of functions that use Layers (808)
fix: Don't set default value for --region (811)

What's New
Lambda functions in a serverless application typically share common dependencies such as SDKs, frameworks, and runtimes. Lambda Layers are a new type of artifact that can contain arbitrary code and data, and may be referenced by multiple functions at the same time. With layers, you can centrally manage common components across multiple functions enabling better code reuse. You can now use AWS SAM and AWS SAM CLI to locally test, deploy and manage serverless applications that leverage Layers.

When you invoke a function (AWS::Lambda::Function or AWS::Serverless::Function) that uses Layers, SAM CLI downloads the layer and makes it available in the container for your function code to use.

Changelog:
fix: AWS CLI on windows can be called aws.cmd or aws.exe (786)
fix: typo in development guide doc (791)
fix: astroid version (795)
fix: Allow local paths for AWS::Lambda::Function (808)
chore: Update aws-lambda-builders (808)
feat: Support Python3.7, Ruby2.5, and Provided Runtimes (808)
feat: Support local testing and debugging of functions that use Layers (808)

What's New

You can now use the `sam build` command to compile deployment packages for AWS Lambda functions written in Python 2.7 and 3.6. If you write code that uses python packages, such as a graphics library for image processing, you need to create a deployment package that will work on the Amazon Linux AMI. The `sam build` command allows you to easily create deployment artifacts that target AWS Lambda's execution environment, so the functions you build locally will run in a similar environment in the cloud.

The `sam build` command iterates through the functions in your application, looks for a manifest file (such as requirements.txt) that contains dependencies, and automatically creates deployment artifacts that you can deploy to Lambda using the `sam package` and `sam deploy` commands. If your functions depend on packages that have natively compiled programs, you can also use the `sam build` command with the `--use-container` flag. This flag builds your functions in a Lambda-like environment locally so they are in the correct format when you deploy them to the cloud.

As part of this release, we have also updated the `sam local invoke` and `sam package` commands to work on built artifacts to streamline the **build -> test -> package -> deploy** workflow. For example, you can execute `sam local invoke` right after executing `sam build` and `sam local invoke` will use the built artifacts. This makes it easier to operate on the template and source code without dealing with intermediate templates.

Changelog
fix: Attempt to recover/invoke function when docker connectivity is poor (764)
feat: Implementation of "sam build" CLI command (766)
feat: "sam package" defaults to built template (775)
feat: Adding a `sam --info` command (776)

Brew for Mac and Linux
You can now install SAM CLI using [brew](https://brew.sh), a popular package manager for installing the packages you need. Installation is as simple as:


brew tap aws/tap
brew install aws-sam-cli

Note: On a Mac you use [Homebrew](https://brew.sh), and on Linux you use [Linuxbrew](http://linuxbrew.sh) (a fork of the Homebrew package manager).

MSI for Windows
You can now download an MSI to install SAM CLI on Windows. Get the MSI you need here:

* [64-bit](https://github.com/awslabs/aws-sam-cli/releases/download/v0.6.2/AWS_SAM_CLI_64_PY3.msi)
* [32-bit](https://github.com/awslabs/aws-sam-cli/releases/download/v0.6.2/AWS_SAM_CLI_32_PY3.msi)

Changelog:

This release also contains the following bug fixes:
- chore(version_bump): bump to 0.6.2
- Fix: Travis times out when running Integ tests (739)
- fix: upgrade requests to 2.20.0 (740)
- Fix typo
- chore: Version bump aws-sam-translator to 1.8.0 (732)
- Update README.rst
- docs: add instructions for using local version of SAM Transformer (688)
- docs: Update Docker command to docker (725)
- fix: Iterate over query param list
- chore: Enable Travis to run integ tests
- fix: Support attaching to host network

Windows 7 and 8 support

SAM CLI now works with Docker Toolbox, so you can now use SAM CLI to test and debug your Lambda functions locally on Windows 7 and 8.

!Ref template parameters locally

We added support for resolving !Ref of template parameters anywhere within a SAM template. You can now provide values for template parameters using the --parameter-overrides CLI option, and reference those within the template. You can also automatically pick up default values of parameters. For example, SAM CLI assigns defaults for CloudFormation pseudo-parameters like AWS::Region.

This release also contains plenty of bug fixes and documentation updates! 🎉

Changelog
---------------
add pytest-mock for testing (703)
fix: allow for stdout and stderr streams to be unbufferred directly. (708)
docs: Add installation instructions for linux (Centos) (670)
fix: Updated isBase64Encoded value to bool (699)
fix: correct launch.json for nodejs debugging through VSCode (704)
docs(usage): Update how to debug Python functions using VS Code (694)
docs(Cloud9): Reset bash cache on Cloud9 (693)
docs: Updated virtualenv alias name for 3.7 in guide. (706)
chore: update aws-sam-translator to 1.7.0 (682)
feat: travis CI support for Python 3.7 (679)
docs: Update generate-sample-event-payloads link (702)
Fix: Raise error for invalid environment variables file (675)
fix: remove dependency on pystache (684)
feat(init): .Net Core 2.1 support for init command (665)
feat(generate-event): Add Kinesis Analytics events (667)
feat(intrinsics): Support !Ref of template parameters (657)
fix: conditionally install enum34 based on python version (671)
fix: Update test format for Nodejs8.10 runtime. (662)
fix: Removed dual line in init help text (664)
docs: Update usage.rst to render code inline (661)
fix(path): change windows style path to unix (633)
fix(docs): fixed macOS name (651)
Fix(generate-event): SubCommand help text to be short-text. (652)
feat(generate-event): Support dns_suffix and partition variables (650)
docs: Consistent packaged template naming (647)
docs(installation): Upgrade instructions for AWS Cloud9 (643)
fix(init): Fix camelCase vs snakeCase issue in NodeJS tests (640)
docs(usage): Update generate-event command structure (638)