feat(decorators): Support Durable Context in logger and metric decorators #7765
+13
−6
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.



Issue number: closes #7762
Summary
This PR updates the Logger and Metric decorators to handle DurableContexts. If a DurableContext is present, it is unwrapped to access the Lambda Context
The
logger.inject_lambda_context()andmetrics.log_metrics()decorators raise an error in some configurations when used with a Durable Execution.The decorators access the Lambda Context. In durable executions, the Lambda Context is wrapped with the Durable Context. The Durable Context is now passed to the handler and thus the decorators.
This affects the
@logger.inject_lambda_context(log_event=True)and@metrics.log_metrics(capture_cold_start_metric=True)decorators (when included params are True). These decorators work without these parameters set. Other decorators do not use the context object, so are not affectedChanges
decorate- Detect if a context is durable or lambda. Extract the lambda contextdecorate- Detect if a context is durable or lambda. Extract the lambda contextdecorate- Detect if a context is durable or lambda. Extract the lambda contextBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.