Source Recurly: Unarchive and release as 1.0 #35763
Merged
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 ↗︎
|
octavia-squidington-iii
added
area/connectors
3 tasks
octavia-squidington-iii
added
the
area/documentation
ChristoGrab
commented
Mar 1, 2024
| message: | ||
| Version 1.0.0 introduces a number of schema updates to the Recurly connector. | ||
| To ensure a smooth upgrade, please refresh your schemas and reset your data before resuming syncs. | ||
| upgradeDeadline: "2024-03-05" |
There was a problem hiding this comment.
Put this date as a placeholder since March 5th was the stated deadline for using the sunsetting connectors. Let me know if this should be changed!
katmarkham
approved these changes
Mar 4, 2024
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
Brings source Recurly back from the archived-connectors repo and into the catalog!
How
Given that:
airbyte-ciI believe the issue lies in the schema changes introduced being backward-incompatible. In that case, the problem should be resolved by having our users go through the usual breaking change migration process and refreshing their schemas/resetting data before resuming syncs.