-
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-paypal-transaction: Keep transaction_id field as a string and shorten step to 7 days #31759
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
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-paypal-transaction test report (commit
|
Step | Result |
---|---|
Build source-paypal-transaction docker image for platform(s) linux/amd64 | ✅ |
Acceptance tests | ✅ |
Check our base image is used | ✅ |
Code format checks | ✅ |
Validate metadata for source-paypal-transaction | ✅ |
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-paypal-transaction test
@@ -6,7 +6,7 @@ | |||
from setuptools import find_packages, setup | |||
|
|||
MAIN_REQUIREMENTS = [ | |||
"airbyte-cdk~=0.1", | |||
"airbyte-cdk>=0.51.44", |
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.
the value_type
field requires 0.51.44
@@ -87,8 +87,9 @@ Transactions sync is performed with default `stream_slice_period` = 1 day, it me | |||
|
|||
| Version | Date | Pull Request | Subject | | |||
|:--------|:-----------|:---------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------| | |||
| 2.1.1 | 2023-10-19 | [31599](https://github.com/airbytehq/airbyte/pull/31599) | Base image migration: remove Dockerfile and use the python-connector-base image | | |||
| 2.1.0 | 2023-08-14 | [29223](https://github.com/airbytehq/airbyte/pull/29223) | Migrate Python CDK to Low Code schema | | |||
| 2.1.2 | 2023-10-23 | [31759](https://github.com/airbytehq/airbyte/pull/31759) | Keep transaction_id as a string and fetch data in 7-day batches | |
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.
this is not a breaking change from 2.1.0, but this is a breaking change from 2.0.0. Considering 2.1.0
is broken, is it worth bumping to 3.0.0
?
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.
we'll also need to update the connection state on cloud because it's pinned to 2.0.0
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.
Considering 2.1.0 is broken, is it worth bumping to 3.0.0?
I'm not sure. I think it would be more fitting to retrospectively mark 2.1.0 as the breaking change 🤔 Then OSS users upgrading to either that version or to the most recent version directly still are aware that the state change is happening. Cloud users we can take care of.
To be clear, the change to state makes it breaking in the "can't roll back" sense, but the roll forward went okay, right?
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.
ah right! the roll forward was fine so no big deal here 👍
retrospectively mark 2.1.0 as the breaking change
Is this just a matter of updating the metadata file with a breaking change block?
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.
Is this just a matter of updating the metadata file with a breaking change block?
It is!
In this case I believe the cloud users would see the banner, since they're currently back on 2.0.0, but I think we can opt in for them? 🤔 Alternatively we could wait until after this PR to mark 2.1.0 as breaking
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.
ok I can mark 2.1.0 as breaking in a follow up PR. I see the deadline is a required field, but would it be valid to set a date in the past?
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.
yep, that's fine!
source-paypal-transaction test report (commit
|
Step | Result |
---|---|
Build source-paypal-transaction docker image for platform(s) linux/amd64 | ✅ |
Acceptance tests | ✅ |
Check our base image is used | ✅ |
Code format checks | ✅ |
Validate metadata for source-paypal-transaction | ✅ |
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-paypal-transaction test
source-paypal-transaction test report (commit
|
Step | Result |
---|---|
Build source-paypal-transaction docker image for platform(s) linux/amd64 | ✅ |
Acceptance tests | ✅ |
Check our base image is used | ✅ |
Code format checks | ✅ |
Validate metadata for source-paypal-transaction | ✅ |
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-paypal-transaction test
What
transaction_id
field was converted to a number. It is now kept as as a string by setting thevalue_type
field in themanifest.yaml
Both issues had to be resolved to get the broken connection to succeed with the new connector.
Recommended reading order
airbyte-integrations/connectors/source-paypal-transaction/source_paypal_transaction/manifest.yaml
airbyte-integrations/connectors/source-paypal-transaction/setup.py
airbyte-integrations/connectors/source-paypal-transaction/metadata.yaml
docs/integrations/sources/paypal-transaction.md
🚨 User Impact 🚨
Pre-merge Actions
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.0.0.1
Dockerfile
has version0.0.1
README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog with an entry for the initial version. See changelog exampledocs/integrations/README.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
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.
Connector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:generateScaffolds
then checking in your changesUpdating the Python CDK
Airbyter
Before merging:
--use-local-cdk --name=source-<connector>
as optionsairbyte-ci connectors --use-local-cdk --name=source-<connector> test
After merging: