source-front: rewrite as native connector #2150
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
Alex-Bair
added
the
change:unplanned
Alex-Bair
force-pushed
the
bair/source-front-native-implementation
branch
from
254e9bf
to
54d5e5c
Compare
williamhbaker
approved these changes
Nov 15, 2024
Alex-Bair
force-pushed
the
bair/source-front-native-implementation
branch
from
54d5e5c
to
167f019
Compare
The `source-front` connector was not working correctly as an import. Instead of troubleshooting the low-code import, I chose to rewrite it as a native connector. Backwards compatibility with the sole existing (non-working) capture was not a goal. I focused on just parent streams that seemed most important for the user's use case, and we can add more later as needed.
Alex-Bair
force-pushed
the
bair/source-front-native-implementation
branch
from
167f019
to
14ef6dc
Compare
This was referenced Nov 15, 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.
Description:
The
source-frontconnector was not working correctly as an import. Instead of troubleshooting the low-code Airbyte import, I chose to rewrite it as a native connector with only a subset of the streams. I focused on parent streams that seemed most important for the user's use case.Backwards compatibility with the single existing, broken capture was not a goal.
The version number has been incremented since the connector is changing from an Airbyte import to a native implementation. Last time I rewrote an import as a native connector, I kept the version number the same and ran into issues with the resource path pointers after deployment. Incrementing the version number should avoid the same issue this time.
Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
Documentation should be created for this connector. I'll link the docs PR here once it's ready.
Notes for reviewers:
Tested on a local stack. Confirmed:
Some streams (primarily
conversationsandeventscan take a while to complete depending on how much data is in the user's Front account.Snapshot changes are expected due to this being a full connector rewrite.
The capture snapshot does not include any documents from the
eventsstream because I couldn't generate any events in the test Front account I created. It's possible Front only generates events for paying customers, although I couldn't find any documentation to support that theory.This change is