AWSLambda.AspNetCoreAppMesh.Catalog
1.0.6.2
dotnet tool install --global AWSLambda.AspNetCoreAppMesh.Catalog --version 1.0.6.2
dotnet new tool-manifest # if you are setting up this repo dotnet tool install --local AWSLambda.AspNetCoreAppMesh.Catalog --version 1.0.6.2
#tool dotnet:?package=AWSLambda.AspNetCoreAppMesh.Catalog&version=1.0.6.2
nuke :add-package AWSLambda.AspNetCoreAppMesh.Catalog --version 1.0.6.2
Catalog Tool Installation
Catalog Tool keeps track of all the running Lambda ASP.NET Core Applications on your local machine that choose to register to recieve incoming InvokeRequest
requests.
dotnet tool install -g AWSLambda.AspNetCoreAppMesh.Catalog
/* to update */
dotnet tool update -g AWSLambda.AspNetCoreAppMesh.Catalog
Run the Catalog Tool
dotnet lambda-app-mesh --urls http://localhost:5050
The --urls
param is optional. The tool will listen on port 5000 and 5001 by default. This is a default port for Kestrel applications so you may want to change it for the Catalog tool.
Once the Catalog Tool is running, your ASP.NET Core applications will be able to register themselves with the catalog. Ensure the catalog url is resolvable and reachable by your applications.
Getting the List of Registered Functions
In a browser, navigate to the URL the Catalog Tool is listening on, such as http://localhost:5050. You will see a list similar to this:
===============================================================================
AWS Lambda ASP.NET Core App Mesh - Catalog
===============================================================================
---------------------------------------------------------------------
| Function Name | Listening On |
---------------------------------------------------------------------
| MyAspNetCoreLambda | http://localhost:63778/lambda-invoke-handler |
---------------------------------------------------------------------
Count: 1
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp3.1 is compatible. |
This package has no dependencies.
v1.0.6.2 - Updated for .NET Core 3.1 (https://aws.amazon.com/blogs/compute/announcing-aws-lambda-supports-for-net-core-3-1/)
v1.0.6 - Removed Razor pages as they were causing issue when running the tool. Tool pkg size reduced.
v1.0.5 - Added support for saving/restoring previously used args (such as --urls)
v1.0.4 - Bumped version due to collision with "1.0.3-alpha"
v1.0.3 - Switch command to dotnet lambda-app-mesh, tested on OSX
v1.0.2 - Donwgraded AWSSDK.Lambda to align with Lambda .NET Core 2.1 LTS runtime environment
v1.0.1 - Don't wait for user input on exit
v1.0.0 - Initial Release