fix(aws-serverless): Take http_proxy
into account when choosing useLayerExtension
default
#17817
+312
−2
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.
The default setting for
useLayerExtension
now considers thehttp_proxy
environment variable. Whenhttp_proxy
is set,useLayerExtension
will be off by default. If you use ahttp_proxy
but would still like to make use of the Sentry Lambda extension, exemptlocalhost
in ano_proxy
environment variable.Fixes: #17804
Note
Disable
useLayerExtension
by default whenhttp_proxy
is set (unlessno_proxy
exempts localhost), add debug warnings, tests, and changelog entry.useLayerExtension
inpackages/aws-serverless/src/init.ts
.shouldDisableLayerExtensionForProxy()
checkshttp_proxy
andno_proxy
(localhost exemptions).packages/aws-serverless/test/init.test.ts
to cover proxy/no_proxy scenarios, explicit overrides, and env cleanup.no_proxy
exemptions.Written by Cursor Bugbot for commit 53e333f. This will update automatically on new commits. Configure here.