-
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
🎉 New Source: Tyntec SMS [low-code cdk] #18883
Conversation
Hello @michizhou, 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:
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. |
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! |
@marcosmarxm Thanks for taking your time to review this. I have DM'ed you on slack with test credentials and to the best of my knowledge I believe I have fulfilled all the checklist items:
|
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.
Some comments.
messages_stream: | ||
$ref: "*ref(definitions.base_stream)" | ||
$options: | ||
name: "messages" | ||
primary_key: "doneDate" | ||
path: "/messaging/v1/messages/{{ config['request_id'] }}" |
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.
Why you don't use the other endpoint to collect all request_id
messgages?
https://api.tyntec.com/reference/sms/current.html#sms-api-Send%20SMS%20(GET)
Are you sure the primary key is DoneDate
?
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.
@marcosmarxm Are you suggesting the linked endpoint is to be used to create a new stream to get request_id
, which would then be passed onto the messages
stream as a parameter? If so, how could I set up such a stream and the messages
stream so they link up properly? The linked endpoint also seems to be designed to send a single SMS message and return the request_id
of the sent message, so I don't know if it can fetch request_id
values of previously sent messages. I suppose we can make it work if we configure it so every SMS message is sent via this new stream and the request_id
is stored or immediately used to trigger the messages
stream.
As for the primary key being doneDate
, the response doesn't have a designated key so I picked it as a reasonable choice. Let me know if you think a different field (or even no field) is more suitable from the response fields: https://api.tyntec.com/reference/sms/current.html#sms-api-restmessageresponse
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.
Exactly. Please read the docs about StreamSlicer: https://docs.airbyte.com/connector-development/config-based/understanding-the-yaml-file/stream-slicers check other connectors implementation using ListStreamSlicer.
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.
Check Survey Sparrow connector, it uses a List StreamSlicer can help you.
request_id: | ||
type: string | ||
title: SMS Message Request ID | ||
description: The unique identifier provided for each SMS messaging request. | ||
order: 1 |
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 think this should be removed and create a new stream to retrieve all requests id/messages and use a stream slices with the message stream.
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.
@marcosmarxm The new stream you suggested to retrieve all request IDs/messages will likely require the addition of new fields to
, from
, and message
, which are required for the linked endpoint. Is this acceptable?
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.
You can implement to
from
but check my previous comment.
@marcosmarxm I have addressed your comments and sent you a DM on Slack with updated test credentials. Please let me know if any additional changes are needed. |
Sorry the delay @michizhou I'll review today! |
/publish connector=connectors/source-tyntec-sms run-tests=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
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 @michizhou I tested locally
* Initial implementation: Support for SMS API streams * Add connector documentation and icon * Add new SMS stream with associated stream slicer * add tyntec sms to source def * format files * auto-bump connector version Co-authored-by: marcosmarxm <marcosmarxm@gmail.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com> Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com>
What
Developing new connector for the source: Tyntec SMS
Documentation: https://api.tyntec.com/reference/sms/current.html#sms-api
Resolves:
🎉 New Source: Tyntec SMS
How
Developed using Low-Code CDK
Recommended reading order
spec.yaml
tyntec_sms.yaml
schemas/messages.json
🚨 User Impact 🚨
No breaking changes. Just the addition of a new source.
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
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.