feat(instrumentation-aws-lambda): use require-in-the-middle
directly
#1314
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.
Which problem is this PR solving?
@opentelemetry/instrumentation-aws-lambda
is incompatible with@opentelemetry/instrumentation@^0.34.0
and higher, since it no longer supports instrumentation of absolute paths. This PR switches to usingrequire-in-the-middle
directly.Fixes #1285
Short description of the changes
This PR replaces usage of
InstrumentationNodeModuleDefinition
andInstrumentationNodeModuleFile
with direct invocation ofrequire-in-the-middle
. Any instrumentation plugins that instrument absolute paths will need to use this strategy; currently, this is the only one.One downside of this approach is that it does not use the normal instrumentation patching infrastructure, so some features (e.g.
instrumentation.disable
) may not work.In #1285, we discussed a few options for resolving the need to instrument absolute paths. This PR represents option 3: