Feature request: ability to specify JMESPath custom functions for Idempotency #2368
Open
1 of 2 tasks
Labels
confirmed
The scope is clear, ready for implementation
feature-request
This item refers to a feature request for an existing or new utility
help-wanted
We would really appreciate some support from community for this one
idempotency
This item relates to the Idempotency Utility
Use case
When working with the JMESPath expressions, the Idempotency utility uses some custom functions (i.e.
powertools_json()
) that extend the JMESPath built-in functions. This allows customers to work with some complex types that are common when working with AWS payloads.The underlying JMESPath utility used by Idempotency however allows for further customization by allowing customers to set additional custom functions in addition or instead of the Powertools-provided ones.
It would be great if customers were able to pass their own subclass of
Functions
orPowertoolsFunctions
when using the Idempotency utility.Solution/User Experience
Currently the Idempotency utility creates its own instance of the
PowertoolsFunctions
class when instantiating theIdempotencyConfig
class. This allows the various components of the utility to reuse it across the implementation.The setting could be exposed to customers by adding a new option to the
IdempotencyConfig
class/object:Alternative solutions
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: