v0.8.2.2

Author: bjorg

.github/workflows/dotnet-core.yml

@@ -0,0 +1,46 @@
+name: LambdaSharp CI/CD
+
+on:
+  push:
+    branches:
+      - main
+      - v*
+      - WIP-v*
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-18.04
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Setup .NET Core
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: 3.1.301
+
+      - name: Set LambdaSharp environment variable
+        run: echo "LAMBDASHARP=$GITHUB_WORKSPACE" >> $GITHUB_ENV
+
+      # CLI Tests
+      - name: Test LambdaSharp.CloudFormation
+        run: dotnet test --configuration Release Tests/Tests.LambdaSharp.CloudFormation
+
+      - name: Test LambdaSharp.Modules
+        run: dotnet test --configuration Release Tests/Tests.LambdaSharp.Modules
+
+      # - name: Test LambdaSharp.Compiler
+      #   run: dotnet test --configuration Release Tests/Tests.LambdaSharp.Compiler
+
+      # SDK Tests
+      - name: Test LambdaSharp
+        run: dotnet test --configuration Release Tests/Tests.LambdaSharp
+
+      - name: Test LambdaSharp.App.EventBus
+        run: dotnet test --configuration Release Modules/LambdaSharp.App.EventBus/Tests.LambdaSharp.App.EventBus
+
+      # Module Tests
+      - name: Test LambdaSharp.Core
+        run: dotnet test --configuration Release Modules/LambdaSharp.Core/Tests/Tests.ProcessLogEventsTests

.gitignore

@@ -16,4 +16,5 @@ cloudformation.json
 # Misc
 .sandbox
 params.yml
-appsettings.Development.json
+appsettings.Development.json
+src/CloudFormationResourceSpecification.json

Docs/articles/APIGateway.md

@@ -37,19 +37,22 @@ MyResponse GetItems(
 ) { ... }
 ```
 
-Common query string parameters can be captured as a class and easily reused across methods. For example, the following class defines the same query string parameters as in the previous example. The determination if a parameter is required is slightly different, because the LambdaSharp CLI cannot determine if a property/field initializer is specified. Therefore, it is necessary to use the `JsonProperty` attribute with the `Required` property to specify if a query parameter is required or not.
+Common query string parameters can be captured as a class and easily reused across methods. For example, the following class defines the same query string parameters as in the previous example. The determination if a parameter is required is slightly different, because the LambdaSharp CLI cannot determine if a property/field initializer is specified. Therefore, it is necessary to use the `JsonPropertyName` attribute with the `Required` property to specify if a query parameter is required or not.
 
 ```csharp
 public class FilterOptions {
 
     //--- Properties ---
-    [JsonProperty(PropertyName = "contains", Required = Required.DisallowNull)]
+    [JsonPropertyName("contains")]
+    [Required]
     public string Contains { get; set; }
 
-    [JsonProperty(PropertyName = "offset", Required = Required.DisallowNull)]
+    [JsonPropertyName("offset")]
+    [Required]
     public int Offset { get; set; } = 0;
 
-    [JsonProperty(PropertyName = "limit", Required = Required.DisallowNull)]
+    [JsonPropertyName("limit")]
+    [Required]
     public int Limit { get; set; } = 10;
 }
 ```
@@ -83,13 +86,13 @@ AddAlbumResponse AddAlbum(
 ) { ... }
 ```
 
-The validation of the request body is controlled by the definition of the `AddAlbumRequest` type. The following type definition makes the `Title` property mandatory while keeping `YearPublished` optional. The constraints of the type fields and properties are controlled using the [JsonProperty](https://www.newtonsoft.com/json/help/html/T_Newtonsoft_Json_JsonPropertyAttribute.htm) and [JsonRequired](https://www.newtonsoft.com/json/help/html/T_Newtonsoft_Json_JsonRequiredAttribute.htm) attributes.
+The validation of the request body is controlled by the definition of the `AddAlbumRequest` type. The following type definition makes the `Title` property mandatory while keeping `YearPublished` optional. The constraints of the type fields and properties are controlled using the [JsonPropertyName](https://docs.microsoft.com/en-us/dotnet/api/system.text.json.serialization.jsonpropertynameattribute) attribute from _System.Text.Json_ namespace, as well as the [Required](https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.dataannotations.requiredattribute) and [Range](https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.dataannotations.rangeattribute) attributes from the _System.ComponentModel.DataAnnotations_ namespace.
 
 ```csharp
 class AddAlbumRequest {
 
     //--- Properties ---
-    [JsonRequired]
+    [Required]
     public string Title { get; set; }
 
     public int? YearPublished { get; set; }

Docs/articles/Events-LambdaError.md

@@ -118,14 +118,6 @@ The <code>AppName</code> property holds the application name.
 <i>Type</i>: String
 </dd>
 
-<dt><code>AppDomainName</code></dt>
-<dd>
-
-The <code>AppDomainName</code> property holds the application domain name.
-
-<i>Type</i>: String
-</dd>
-
 <dt><code>Platform</code></dt>
 <dd>
 

Docs/articles/ReleaseNotes-Hicetas.md

@@ -4,7 +4,7 @@ description: Release notes for LambdaSharp "Hicetas" (v0.8)
 keywords: release, notes, hicetas
 ---
 
-# LambdaSharp "Hicetas" Release (v0.8.2.1) - 2021-02-17
+# LambdaSharp "Hicetas" Release (v0.8.2.2) - 2021-03-17
 
 > Hicetas was a Greek philosopher of the Pythagorean School. He was born in Syracuse. Like his fellow Pythagorean Ecphantus and the Academic Heraclides Ponticus, he believed that the daily movement of permanent stars was caused by the rotation of the Earth around its axis. When Copernicus referred to Nicetus Syracusanus (Nicetus of Syracuse) in _De revolutionibus orbium coelestium_ as having been cited by Cicero as an ancient who also argued that the Earth moved, it is believed that he was actually referring to Hicetas. [(Wikipedia)](https://en.wikipedia.org/wiki/Hicetas)
 
@@ -141,6 +141,21 @@ Part of this release, _LambdaSharp.Core_ functions were ported to .NET Core 3.1
 
 ## Releases
 
+### (v0.8.2.2) - 2021-03-17
+
+#### BREAKING CHANGES
+
+* SDK
+    * Renamed _LambdaSharp.CloudWatch_ assembly to _LambdaSharp.EventBridge_ to align with new AWS branding for CloudWatch Events.
+
+#### Features
+
+* CLI
+  * Added automatic, daily refresh of CloudFormation specification to surface latest capabilities. Use `--force-refresh` option to check for new CloudFormation specification more frequently.
+  * Added caching of AWS profile information used for building, publishing, and deploying modules. Use `--force-refresh` option to bypass cache.
+  * Removed `util download-cloudformation-spec` command since it is no longer needed to CloudFormation specification.
+  * Changed behavior for `deploy` to allow importing dependencies when no build policy is provided.
+
 ### (v0.8.2.1) - 2021-02-17
 
 #### Fixes
@@ -192,7 +207,7 @@ Part of this release, _LambdaSharp.Core_ functions were ported to .NET Core 3.1
 
 * CLI
   * Added support for self-contained .NET 5 Lambda functions.
-  * Update Blazor WebAssembly app template to target .NET 5.
+  * Updated Blazor WebAssembly app template to target .NET 5.
   * Removed dependency on _Amazon.Lambda.Tools_. _Amazon.Lambda.Tools_ is no longer requires to build, publish, or deploy LambdaSharp modules.
   * Updated CloudFormation to v22.0.0.
   * Allowed resource types to have an empty or omitted `Attributes` section.

Docs/articles/VideoTutorials.md

@@ -6,6 +6,8 @@ keywords: video, tutorial, getting started, overview
 
 # Video Tutorials
 
+Subscribe to the [LambdaSharp YouTube channel](https://www.youtube.com/channel/UC9zH5HkC6dHvuFJR6_XZzFg) to stay up-to-date on the latest videos.
+
 ## Getting Started
 
 It's easy to get started building Serverless .NET application on AWS with LambdaSharp. In in this 10 minute tutorial, we will install the LambdaSharp CLI, create a configuration for it, and a deployment tier for your LambdaSharp modules. Along the way, I will explain what resources are part of the configuration and deployment tier and what purpose they play.
@@ -22,4 +24,10 @@ In this video, I'm going through the steps for creating your first Serverless .N
 
 Learn how you can build and deploy your serverless solution in minutes using LambdaSharp, an open-source CLI and framework for serverless .NET Core application development on AWS. The solution shares the same C# code for the backend and front end leveraging AWS Lambda functions and the Blazor WebAssembly framework. Finally, see a demonstration of how easy it is to integrate with Amazon CloudWatch Logs, metrics, and Amazon EventBridge.
 
-<iframe width="560" height="315" src="https://www.youtube.com/embed/wN_0mQ7AUg8" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/wN_0mQ7AUg8" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+## Serverless .NET Patterns: Service Composition
+
+This presentation covers some of the serverless design patterns, such as CQRS (Command and Query Responsibility Separation), CloudFormation stacks, sharing of resources, nested vs. side-by-side composition, and then put it all together with some code samples found at: https://github.com/LambdaSharp/ServerlessPatterns-ServiceComposition
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/P8o7ZI8XCRg" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

Docs/articles/toc.yml

@@ -48,13 +48,16 @@
 - name: Debugging
   href: Debugging.md
 
+- name: JSON Serialization
+  href: JSON-Serialization.md
+
 - name: Samples
   href: Samples.md
 
 - name: Releases
   items:
 
-    - name: Hicetas (v0.8.2.1)
+    - name: Hicetas (v0.8.2.2)
       href: ReleaseNotes-Hicetas.md
 
     - name: Geminus (v0.7.0.17)

Docs/cli/Index.md

@@ -35,7 +35,6 @@ The LambdaSharp CLI is used to process the module definition, compile the C# pro
 ## Utility Commands
 1. [`util create-invoke-methods-schema`](Tool-Util-CreateInvokeMethodsSchema.md): create JSON schema for compiled methods
 1. [`util delete-orphan-logs`](Tool-Util-DeleteOrphanLogs.md): delete orphaned Lambda CloudWatch logs
-1. [`util download-cloudformation-spec`](Tool-Util-DownloadCloudFormationSpec.md): download the CloudFormation types specification
 1. [`util list-lambdas`](Tool-Util-ListLambdas.md): list Lambda functions by CloudFormation stack
 1. [`util list-modules`](Tool-Util-ListModules.md): list published LambdaSharp modules at an origin
 1. [`util show-kinesis-failed-logs`](Tool-Util-ShowKinesisFailedLogs.md): show the failed Kinesis Firehose records from the S3 logging bucket

Docs/cli/Tool-Build.md

@@ -85,6 +85,12 @@ lash build
 (optional) Always build function packages
 </dd>
 
+<dt><code>--force-refresh</code></dt>
+<dd>
+
+(optional) Always refresh manifests from their origin
+</dd>
+
 <dt><code>--build-policy &lt;FILEPATH&gt;</code></dt>
 <dd>
 

Docs/cli/Tool-Deploy.md

@@ -165,6 +165,12 @@ If the argument refers to a module definition, the `deploy` command invokes the
 (optional) Always build function packages
 </dd>
 
+<dt><code>--force-refresh</code></dt>
+<dd>
+
+(optional) Always refresh manifests from their origin
+</dd>
+
 <dt><code>--build-policy &lt;FILEPATH&gt;</code></dt>
 <dd>