feat: pick objects to revalidate via API #180
Merged
Conversation
This file contains hidden or 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
Instead of an all or nothing revalidation, it is now possible to define the entities that shall be refetched via Stripe API before syncing. This adds some flexibility on what entities should be refetched or not.
ignaciodob
approved these changes
Sep 4, 2025
|
🎉 This PR is included in version 0.41.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Instead of an all or nothing revalidation, it is now possible to define the entities that shall be refetched via Stripe API before syncing. This adds some flexibility on what entities should be refetched or not.
Also fixes the sync timestamp not being set properly in case of revalidation
Entities can be configured via env var
REVALIDATE_OBJECTS_VIA_STRIPE_API