-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source GCS: Migrated to file based CDK #31212
Source GCS: Migrated to file based CDK #31212
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice @lazebnyi! Just one minor comment & question in the code.
A couple of requests for tests:
- Since the file-based CDK supports incremental syncs, I assume we'll start supporting incremental for GCS (unless we're planning to turn it on later and hide it in the UI somehow until then). Can you add some CATs covering incremental? You can look at the S3 tests for examples.
- Have the configs been migrated to the new format yet? I think we'll want CATs that run the new code with both the old and new formats.
airbyte-integrations/connectors/source-gcs/integration_tests/configured_catalog.json
Show resolved
Hide resolved
airbyte-integrations/connectors/source-gcs/integration_tests/spec.json
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
source-gcs test report (commit
|
Step | Result |
---|---|
Build source-gcs docker image for platform(s) linux/amd64 | ✅ |
Unit tests | ✅ |
Acceptance tests | ✅ |
Code format checks | ✅ |
Validate metadata for source-gcs | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
☁️ View runs for commit in Dagger Cloud
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-gcs test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @lazebnyi!
As we discussed, please follow up with a PR to move the cursor logic into the file-based CDK, and a second PR updating this connector so that we don't have to copy over the cursor methods.
What
Fixed #29831
Need to migrate connector into a scalable and easy-to-manage connector.
How
Migrated connector to file based CDK
🚨 User Impact 🚨
No
Pre-merge Actions
Updating a connector
Community member or Airbyter
NOTE: UNIT TESTS IN PREGRESS
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.