chore(libraries): add jmespath as a required dependency #4422
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: #4340
Summary
Changes
This pull requests addresses an issue where the Logger utility/and others fails to work due to missing jmespath dependency.
The issue occurs in environments that are not AWS Lambda/emulations, as these environments already include the jmespath library by default. However, when running the Logger utility in other environments, such as local development or non-Lambda deployments, the
ModuleNotFoundError: No module named 'jmespath'
error is raised due to the missing dependency.User experience
Customers now do not need to install jmespath after installing the Powertools package.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By 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.