Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SAM build continually updates Lambda Tools

Open
#347 8 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws
Domain
build-system, cloud

Research direction

Start by reproducing the issue with SAM CLI 1.40.1 using sam build on OSX, then trace the Amazon.Lambda.Tools installation and update path shown in the log. Done means an already-installed version such as 5.3.0 is recognized and sam build no longer repeatedly updates it on subsequent builds.

Written by the indexing model from the issue text.

Description

area/workflow/dotnet_clipackage stage/pr type/feature

Description:
Hello AWS, is there a way to disable sam build from trying to update the lambda tools? I have the latest installed and it continually tries to upgrade them but this takes several minutes each sam build. You can see in the log below that it says it is successful in the upgrade but when I run sam build again, it again upgrades the tools (to the same version). This is causing significant development delays in my workflow so I was wondering if there is a way to disable this feature?

Installing Amazon.Lambda.Tools Global Tool
2022-03-18 09:28:12,947 | executing dotnet: ['dotnet', 'tool', 'install', '-g', 'Amazon.Lambda.Tools', '--ignore-failed-sources']
2022-03-18 09:28:13,170 |
2022-03-18 09:28:13,170 | Error installing probably due to already installed. Attempt to update to latest version.
2022-03-18 09:28:13,170 | executing dotnet: ['dotnet', 'tool', 'update', '-g', 'Amazon.Lambda.Tools', '--ignore-failed-sources']
2022-03-18 09:30:49,724 | Tool 'amazon.lambda.tools' was reinstalled with the latest stable version (version '5.3.0').
2022-03-18 09:30:49,724 | DotnetCliPackageBuilder:GlobalToolInstall succeeded

As a side note, I have uninstalled and reinstalled the tools several times with dotnet tools directly which doesn't seem to fix the issue.

SAM build continually upgrades the AWS Lambda Tools and doesn't recognize that it has installed the latest already.

Steps to reproduce the issue:

  1. sam build

Observed result:
SAM doesn't detect the latest version of lambda tools is already installed in the global space
Expected result:
SAM should not try to upgrade the tools when it is already running the latest.

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Osx, SAM CLI version 1.40.1

Dominant language
Python
Stars
381
Forks
162
Avg merge
1d 1h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-builders

All issues in aws/aws-lambda-builders

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.