Skip to content

Add variable to disable instrumentation #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

clementdenis
Copy link

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:

  • It requires duplicated configuration for both regular and wrapped lambda
  • enabling / disabling instrumentation would recreate the lambda (unless doing a manual move operation)

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.

@clementdenis clementdenis requested a review from a team as a code owner August 7, 2025 08:40
@clementdenis clementdenis requested a review from ava-silver August 7, 2025 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant