feat: allow explicit listing of function ids for local start-lambda command#8392
Merged
vicheey merged 11 commits intoNov 11, 2025
Merged
Conversation
vicheey
marked this pull request as ready for review
November 3, 2025 21:06
start-lambda command
vicheey
force-pushed
the
feat-allow-specifying-functions-local-start-command
branch
from
November 4, 2025 01:28
c100003 to
3b5fbbb
Compare
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
licjun
reviewed
Nov 5, 2025
tobixlea
previously approved these changes
Nov 5, 2025
vicheey
commented
Nov 5, 2025
valerena
reviewed
Nov 11, 2025
licjun
previously approved these changes
Nov 11, 2025
tobixlea
previously approved these changes
Nov 11, 2025
vicheey
commented
Nov 11, 2025
valerena
approved these changes
Nov 11, 2025
licjun
approved these changes
Nov 11, 2025
vicheey
deleted the
feat-allow-specifying-functions-local-start-command
branch
November 13, 2025 19:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Which issue(s) does this change fix?
Enables developers to specify a subset of Lambda functions from the template when starting local development servers.
Why is this change necessary?
This is for improving development efficiency by reducing resource usage and startup time for large SAM applications.
When working with SAM templates containing many Lambda functions, developers often only need to test a few functions at a time. Currently,
sam local start-lambdainitialize containers for ALL functions in the template when using--warm-containers EAGER, which:This change allows developers to specify exactly which functions they want to work with, similar to how they can already target specific functions with
sam local invoke.How does it address the issue?
Adds function name filtering capability to
sam local start-lambdacommands so that users can now runsam local start-lambda Function1 Function2CLI Changes
invoke_context.py):function_logical_idsparametersam_function_provider.py):Testing
What side effects does this change have?
Additive Feature
Backward compatibility
Mandatory Checklist
PRs will only be reviewed after checklist is complete
make prpassesmake update-reproducible-reqsif dependencies were changedHelp Document Update
sam local start-lambda --helpHelp Document Update
sam local start-api --helpBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.