-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
🎉 New Source: EmailOctopus [low-code cdk] #18647
Conversation
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.
Hello @scottleechua, Marcos from Airbyte here 👋 . We received more than 25 new contributions along the weekend. One is yours 🎉 thank so much for! Our team is limited and maybe the review process can take longer than expected. As described in the Airbyte's Hacktoberfest your contribution was submitted before November 2nd and it is eligible to win the prize. The review process will validate other requirements. I ask to you patience until someone from the team review it.
Because I reviewed some contributions for Hacktoberfest so far I saw some common patterns you can check in advance:
- Make sure you have added connector documentation to
/docs/integrations/
- Remove the file
catalog
from/integration_tests
- Edit the
sample_config.json
inside/integration_tests
- For the
configured_catalog
you can use onlyjson_schema: {}
- Add title to all properties in the
spec.yaml
- Make sure the
documentationUrl
in thespec.yaml
redirect to Airbyte's future connector page, eg: connector Airtable thedocumentationUrl: https://docs.airbyte.com/integrations/sources/airtable
- Review now new line at EOF (end-of-file) for all files.
If possible send to me a DM in Slack with the tests credentials, this process will make easier to us run integration tests and publish your connector. If you only has production keys, make sure to create a bootstrap.md explaining how to get the keys.
@scottleechua please ask my review when you solve all points I have made in my previous comment. |
Hello! I'm going to be out of the office this Friday and won't be able to review your contribution again today, I return next Monday. So far, most contributions look solid and are almost done to be approved. As said in Chris' comment all contributions made before 2-November are eligible to receive the prize and have 2 weeks to merge the contributions. But I ensure next week we're going to have your contribution merged. If you have questions about the implementation you can send them in Sorry the inconvenience and see you again next week, thank you so much for your contribution! |
Hello @marcosmarxm , @sajarin !
Also am not sure why the acceptance tests run by @koconder failed as Thank you! 😄 |
@scottleechua ignore the earlier test results from my side. They did have test credentials setup. Appologies for the confusion caused. |
Ah, got it! All good @koconder 😄 |
Thanks @scottleechua I'm waiting EmailOctopus approve my account to test your connector. I'll return the review tomorrow. |
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.
Thanks @scottleechua for the contribution
/test connector=connectors/source-emailoctopus
Build PassedTest summary info:
|
/publish connector=connectors/source-emailoctopus
if you have connectors that successfully published but failed definition generation, follow step 4 here if you have connectors that successfully published but failed definition generation, follow step 4 here |
…s/TODO, remove EOF newlines
/publish connector=connectors/source-emailoctopus
if you have connectors that successfully published but failed definition generation, follow step 4 here |
* Initial commit - emailoctopus * Add API key parameter * Update schemas * Annotate schemas * Update integration tests * Acceptance test bug fixes * Change full refresh append to overwrite; delete abnormal state * Add documentation * Update documentation * Update documentation * Update DocumentationUrl, add titles to spec properties, remove schemas/TODO, remove EOF newlines * Add BOOTSTRAP.md * Remove todos * run format * add emailloctopus to source def * run format * auto-bump connector version Co-authored-by: marcosmarxm <[email protected]> Co-authored-by: Octavia Squidington III <[email protected]>
What
This PR adds a source connector for EmailOctopus. Please see this issue for more context.
How
This PR uses the low-code CDK to create a source connector for the critical streams:
Recommended reading order
docs/integrations/sources/emailoctopus.md
spec.yaml
emailoctopus.yaml
schemas/campaigns.json
andschemas/lists.json
🚨 User Impact 🚨
No changes to base code.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereTests
Acceptance