add revalidation flag for apple receipts revalidation lambda #1453
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is the first in a string of PRs, this currently adds a revalidation flag to the apple receipts revalidation lambda. this revalidation flag needs to be added to downstream lambdas.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this change?
This is the first in a string of PRs, this currently adds a revalidation flag to the apple receipts revalidation lambda. this revalidation flag needs to be added to downstream lambdas.
Once this is implemented it will allow the
mobile-purchases-apple-update-subscriptionslambda to make less calls out to braze and dynamo as it already had the revalidation data.How to test
This was tested locally with tests and also using tests in the CODE environment.
How can we measure success?
Have we considered potential risks?
Images
Accessibility