aws-extensions-for-dotnet-cli: Amazon.Lambda.Tools 5.12.1 breaks application publishing

Describe the bug

I have a toy application targeting .NET 9 that is deployed to both AWS Lambda as a custom runtime function and Azure App Service as a container.

A dependabot PR (https://github.com/martincostello/adventofcode/pull/1980) updating Amazon.Lambda.Tools from 5.12.0 to 5.12.1 breaks publishing the application on Linux and Windows with one error and on macOS with a different error.

Linux and Windows

Amazon Lambda Tools for .NET Core applications (5.12.1)
Project Home: https://github.com/aws/aws-extensions-for-dotnet-cli, https://github.com/aws/aws-lambda-dotnet
	
Host machine architecture (X64) differs from Lambda architecture (Arm64). Building Native AOT Lambda functions require the host and lambda architectures to match.

macOS

Amazon Lambda Tools for .NET Core applications (5.12.1)
Project Home: https://github.com/aws/aws-extensions-for-dotnet-cli, https://github.com/aws/aws-lambda-dotnet
	
No container build image available for targetFramework net9.0 and architecture arm64.

The tooling should not block the publish as the application is authored in a way that a working native AoT application is produced that works for an ARM64 custom runtime function.

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

The lambda ZIP archive is produced for deployment.

Current Behavior

Publishing the application fails.

Reproduction Steps

  1. Clone https://github.com/martincostello/adventofcode/pull/1980/commits/d3e9a00e6ebf4d54836eab9cd59df48128fd1b3f
  2. Run build.ps1 -SkipTests from the root of the repository

Possible Solution

No response

Additional Information/Context

No response

Targeted .NET platform

.NET 9

CLI extension version

amazon.lambda.tools 5.12.1

Environment details (OS name and version, etc.)

Any

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (14 by maintainers)

Commits related to this issue

Most upvoted comments

Thanks for the confirmation and the help addressing the issue.

Thanks @martincostello. We’ll get the PR released.

Here is the PR to include the --msbuild-parameters value when evaluating MSBuild properties. When we get past our restricted change control for re:Invent I’ll get this released.