-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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-shopify: ensure inline schemas, updated cdk, poetry (where possible) #36660
source-shopify: ensure inline schemas, updated cdk, poetry (where possible) #36660
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -17,7 +17,7 @@ include = "source_shopify" | |||
|
|||
[tool.poetry.dependencies] | |||
python = "^3.9,<3.12" | |||
airbyte-cdk = "^0" | |||
airbyte-cdk = "0.81.4" |
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 should not be changed.
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.
It's a change, I understand, but this looks to be better than what's happening with the open pinning. causing less issues.
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 actual code in use has not changed.
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.
If there are no functional changes, i don't think the source bump should take place either, we can safely merge this without source version bump, these changes than be picked up later on with the next functional change (bug fix or improvements).
The cdk version pin will not help us later on when we want to be able to update the sources with the latest functionality causing to bump each and every source again.
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.
but I also updated all the descriptions
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.
do we plan to use these descriptions in UI or elsewhere making this visible for Customers or any kind of functionality for the platform?
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.
I assume the formatting issue should pass. Can we re-run this? Else, LGTM so this is a conditional approval!
/format-fix
|
The format check issues should be auto-formatted and committed after the |
/format-fix
|
This was created from a set of automated scripts. In each case, not every update was needed for every connector, but overall here is what happened:
auto-schema update -s all description
: added descriptions to json and inline schemasconnector-code migrate_to_yaml -c all --type source
: migrates json schemas to connectors with a manifestairbyte-ci connectors --name=<all modified connectors from above> migrate_to_base_image
: makes sure that each is using a base docker image and updates docsairbyte-ci connectors --name=<all modified connectors from above> migrate-to-poetry
: moves connectors not already using poetry to do so and updates documentationairbyte-ci connectors --name=<all modified connectors from above> up_to_date
: updated the CDK to newer (0.80.0) versionThe version number and changelogs were also bumped using the
connector-code pulls
command.