-
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 Weatherstack - Migrate Python CDK to Low-code CDK #43298
Conversation
…pe/migrate-weatherstack-lowcode
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 good, thank you @topefolorunso!
A few things I noted:
- https URLs everywhere. HTTP will not (and did not) pass the validation.
- Fix the formatting (
/format-fix
would do that) - Use standard
YamlDeclarativeSource
wrapper. Don't remove two streams for free accounts. In fact, I would remove theis_paid_account
config input altogether, and just set an error handler to ignore HTTP 403 on those two streams.
@ChristoGrab and I are happy to help with the error handler if that gets tricky.
airbyte-integrations/connectors/source-weatherstack/source_weatherstack/manifest.yaml
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-weatherstack/source_weatherstack/source.py
Outdated
Show resolved
Hide resolved
…pe/migrate-weatherstack-lowcode
Minimal tests are passing! I would call this a 1.0.0, drop |
all done @natikgadzhi. please see if the breaking change was done properly |
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.
Code looks good.
What
Migrate Weatherstack Python CDK to Low-code CDK fixes https://github.com/airbytehq/airbyte-internal-issues/issues/8958
How
Developed using UI Builder and the Low-code CDK
Recommended reading order
manifest.yaml
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user?
For connector PRs, use this section to explain which type of semantic versioning bump occurs as a result of the changes. Refer to our Semantic Versioning for Connectors guidelines for more information. Breaking changes to connectors must be documented by an Airbyte engineer (PR author, or reviewer for community PRs) by using the Breaking Change Release Playbook.
If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Actions
Expand the relevant checklist and delete the others.
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.