Add variable to disable instrumentation #44
+10
−4
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.
I want to be able to enable or disable instrumentation for my lambdas selectively based on which environment I deploy to.
It's currently inconvenient to do so using this module, as I would need to have a regular lambda resource when deploying without instrumentation, but would need to use the module when enabling. That's definitely possible using conditional activation with count attributes, but:
This PR adds a single
disable_instrumentation
variable to disable all customizations performed by the module, acting as a pass-through wrapper for the aws_lambda_function resource.