fix(idempotency): idempotent_function should support standalone falsy values #1669
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: #1663
Summary
When using
idempotent_function
for any synchronous Python function (different from Lambda Handler), customers set which keyword argument we should use to hash data as an idempotency key.We raise
RuntimeError
for cases where the keyword argument wasn't used correctly to prevent hashing the incorrect data. For example, function was called without the keyword argument (function()
, instead offunction(data=data)
).However, the current logic incorrectly checks the value available in the keyword argument, rather than the keyword argument was used. The following code leads to a
RuntimeError
when we should be serializingNone->null
just fine.Changes
This PR corrects the logic and only raises
RuntimeError
if the keyword argument specified for hashing isn't in the list of keyword arguments available at the function call.User experience
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.