jbranchaud/tjs 62 Make EW stripe webhook handler deal with TJS stripe events #1427
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jbranchaud
changed the title
…hook-endpoint-to-list-of-stripe
kodiakhq
bot
deleted the
jbranchaud/tjs-62-add-testing-javascript-webhook-endpoint-to-list-of-stripe
branch
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.
Note: I've tested this locally against TT, EW and TJS. All looks good.
This PR makes some updates to Stripe webhook handling in the skill-api. The
epic-webapp receives stripe webhook events for all kcd-products. For the events that are for one of the other kcd-products (e.g. testing-javascript), they will be forwarded along to that app so that it can process them in the proper context (that context is important for things like sending emails).We know what app a webhook is meant for because we include the
siteNamein the webhook metadata. At this point, this is mainly relevant forcustomer.updatedandcheckout.session.created.