Aws-sam-cli

You can now use the `sam build` command to create deployment packages for AWS Lambda functions written in Java using the Maven build tool.

In addition, `sam init` was expanded to support creating projects with different dependency managers. You can now create a Maven example by running `sam init --runtime java --dependency-manager maven`. See `sam init --help` for other supported values for the `--dependency-manager` Option.

Huge shoutout to zoewangg for contributing the Maven builder

Changelog
Chore: Bump aws-sam-translator to 1.10.0 (1043)
feat(init): gradle init support (1040)
feat(build): Support building Java8 functions through Maven (1044)
feat(publish): Add --semantic-version option to sam publish command (1020)

What's New?
You can now use the `sam build` command to create deployment packages for AWS Lambda functions written in Java using the Gradle build tool.

Huge shoutout to dagnir for contributing the Gradle builder

Changelog
* Accept non-integer statusCode JSON values (1013)
* feat(build): Support for building Java functions using Gradle (1007)
* tests(integ): adding integ test for aws config and profile env vars (1004)
* feat: allow sam to be invoked as a module (987)
* refactor(build): Move workflow config information into its own file (1001)
* chore: Bump aws-sam-transform to 1.9.1 (990)
* docs: Fix Nodejs references in Python Cookiecutter README (986)
* fix(init): Make template spacing consistent (962)
* docs(init): typo fix in Go README.md (971)

What's New?
This release contains numerous improvements throughout the CLI, including simpler hello world quickstarts, doc updates, removing unnecessary compression when building a layer image for invoking, and cleaning up build containers.

Changelog
* fix(publish): fix integ test metadata and templates (982)
* fix(publish): fix failing integ tests due to .rst to .md file changes (981)
* chore(release): Bump version to 0.11.0 (979)
* refactor(logging): Add additional information when function not found (977)
* fix: update license key in setup() to expected value by PyPi (966)
* chore: add required options for package and deploy (961)
* feat(layers): remove compression of docker context (862)
* docs: remove maxage off badges (943)
* fix: translate paths in SAR metadata during sam build (935)
* docs: update sam package command in cookiecutter docs (919)
* fix(build): cleanup build containers (929)
* refactor: simplify built-in quickstarts to a simple hello world (849)
* feat(invoke): reading Metadata adding to Resources in a template (907)
* docs(design): Debugging .NET Core Lambda Functions (759)
* refactor: fix grammar in log statement (800)
* docs(design): sam publish command (844)
* fix links to .md files (915)
* chore: remove dangling rst file (905)
* fix: formatting to md from rst (891)

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

You can now also use the new `sam publish` command to publish your serverless application to the AWS Serverless Application Repository, a managed repository for serverless applications. The AWS Serverless Application Repository enables teams, organizations, and individual developers to store and share reusable applications, and easily assemble and deploy serverless architectures in powerful new ways. To publish an application using SAM CLI, first define necessary application details like application name, description, semantic version, and license information using the `AWS::ServerlessRepo::Application` Key in the `Metadata` section of your SAM template. Then, use the `sam publish` command to make your application available in the AWS Serverless Application Repository for others to consume. To learn more, please visit the [sam publish documentation](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-template-publishing-applications.html). Huge shout-out to paoptu023 for this contribution!

Changelog
* Implement sam publish app command (852)
* Add Ruby to Supported Runtime Enum (866)
* fix: Flush stdout and stderr on each write when debugging (843)
* chore(version): bump version to 0.10.0 (881)

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)