tiny increase of lambda layer size limit#760
Merged
emmettbutler merged 3 commits intomainfrom Mar 27, 2026
Merged
Conversation
Co-authored-by: Brett Langdon <brett.langdon@datadoghq.com>
brettlangdon
approved these changes
Mar 26, 2026
purple4reina
approved these changes
Mar 26, 2026
Contributor
purple4reina
left a comment
purple4reina
left a comment
There was a problem hiding this comment.
That seems like an acceptable number.
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
3 participants
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.
What does this PR do?
This pull request adds nine kilobytes to the lambda layer size limit to accommodate recent changes in dd-trace-py, visible here: https://gitlab.ddbuild.io/DataDog/datadog-lambda-python/-/jobs/1540965039
Motivation
This size check failure is currently blocking the dd-trace-py release.