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 Pipedrive: Remove followers_count
field from Products
stream
#27832
Conversation
Before Merging a Connector Pull RequestWow! What a great pull request you have here! 🎉 To merge this PR, ensure the following has been done/considered for each connector added or updated:
If the checklist is complete, but the CI check is failing,
|
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ❌ |
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-pipedrive test
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ✅ |
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-pipedrive 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.
@artem1205 does keeping the field in the schema is causing a sync issue?
No, as we don't receive it in response. |
Would you mind publishing a pre-release and try it on a connection with the previous version to check if the column is deleted on the destination side? I believe normalization to be non destructive so hopefully the destination column is not deleted. Moreover if schema change is detected the user will be notified about this change. If it's still available on the destination we can move forward without a breaking change process |
May I check this locally using Postgres? |
Yes sure, just make sure to first create and run a sync with 0.1.18 and then upgrade to 1.0.0 and share the results 🙏 Thanks! |
followers_count
field from Products
stream
Actions Made
Test Resultscolumn is deleted |
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ❌ |
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-pipedrive test
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ❌ |
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-pipedrive test
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ✅ |
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-pipedrive test
@artem1205 if the destination column was deleted by normalization please fill out start a breaking change procedure by creating a new document following this template: https://docs.google.com/document/d/1VYQggHbL_PN0dDDu7rCyzBLGRtX-R3cpwXaY8QxEgzw/edit#heading=h.r2xzw0kclodc This is a breaking change because on connector upgrade the customer will lose data... |
# Conflicts: # airbyte-integrations/connectors/source-pipedrive/Dockerfile # airbyte-integrations/connectors/source-pipedrive/integration_tests/expected_records.jsonl # airbyte-integrations/connectors/source-pipedrive/metadata.yaml # docs/integrations/sources/pipedrive.md
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ❌ |
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-pipedrive test
source-pipedrive test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-pipedrive/metadata.yaml | ✅ |
Connector version semver check | ✅ |
Connector version increment check | ✅ |
QA checks | ✅ |
Code format checks | ✅ |
Connector package install | ✅ |
Build source-pipedrive docker image for platform linux/x86_64 | ✅ |
Unit tests | ✅ |
Integration tests | ✅ |
Acceptance tests | ✅ |
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-pipedrive test
What
Fix Source Pipedrive Connector Health
How
Recommended reading order
expected_records.jsonl
products.json
🚨 User Impact 🚨
Products
schema changed; schema update requiredPlaybook: https://docs.google.com/document/d/16rwD7XEstml1TiW8PH6mjk00q0vynlHDL0TvWPEG0io/edit
Pre-merge Actions
Updating a connector
Community member or Airbyter
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.