airbyte
airbyte copied to clipboard
🐛 Source Aircall: Fixing aircall incrementals
What
This PR is to achieve a couple of things.
- fixing the pagination
- adding incremental sync for calls and contacts (the only two that have enough volume to warrant incremental and or support it.
- removing incremental for teams as this does not support incremental https://developer.aircall.io/api-references/#team-overview
How
Describe the solution
Recommended reading order
-
x.java
-
y.python
🚨 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.
New Connector
Community member or Airbyter
- Community member? Grant edit access to maintainers (instructions)
- Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
. - Connector version is set to
0.0.1
-
Dockerfile
has version0.0.1
-
- Documentation updated
- Connector's
README.md
- Connector's
bootstrap.md
. See description and examples -
docs/integrations/<source or destination>/<name>.md
including changelog with an entry for the initial version. See changelog example -
docs/integrations/README.md
- Connector's
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
- Create a non-forked branch based on this PR and test the below items on it
- Build is successful
- If new credentials are required for use in CI, add them to GSM. Instructions.
Updating a connector
Community member or Airbyter
- Grant edit access to maintainers (instructions)
- Unit & integration tests added
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
- Create a non-forked branch based on this PR and test the below items on it
- Build is successful
- If new credentials are required for use in CI, add them to GSM. Instructions.
Connector Generator
- Issue acceptance criteria met
- PR name follows PR naming conventions
- If adding a new generator, add it to the list of scaffold modules being tested
- The generator test modules (all connectors with
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changes - Documentation which references the generator is updated as needed
Before Merging a Connector Pull Request
Wow! 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:
- [ ] PR name follows PR naming conventions
- [ ] Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
- [ ] Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
- [ ] You've updated the connector's
metadata.yaml
file any other relevant changes, including abreakingChanges
entry for major version bumps. See metadata.yaml docs - [ ] Secrets in the connector's spec are annotated with
airbyte_secret
- [ ] All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
- [ ] Changelog updated in
docs/integrations/<source or destination>/<name>.md
with an entry for the new version. See changelog example - [ ] Migration guide updated in
docs/integrations/<source or destination>/<name>-migrations.md
with an entry for the new version, if the version is a breaking change. See migration guide example - [ ] If set, you've ensured the icon is present in the
platform-internal
repo. (Docs)
If the checklist is complete, but the CI check is failing,
-
Check for hidden checklists in your PR description
-
Toggle the github label
checklist-action-run
on/off to re-run the checklist CI.
@marcosmarxm would it possible to get a review on this
@jhsb25 right now the team is dedicated to review August Hackathon contributions. We're going to return to the community backlog after the event finish
@jhsb25 right now the team is dedicated to review August Hackathon contributions. We're going to return to the community backlog after the event finish
@marcosmarxm has there been any movement on this, would really like to get this merged
@marcosmarxm can i please get an approval on this?
Hello @jhsb25 sorry the lack of updates for your contribution. This week the codebase is freeze because of holidays but I'll start the process of running tests and return to you asap.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
airbyte-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 12, 2024 5:41pm |
@jhsb25 @marcosmarxm Do we have an update here on when you can merge it
@marcosmarxm any update on this?
The current Aircall integration tests are failing multiple tests and need someone from the team to fix them. This is in the team backlog but don't have a timeline to release a fix. Any updates return to you here, thanks for the patience.
Hello ! Any update on this ? My team and I are waiting for this fix 🙏 Thanks 🙏
@marcosmarxm is there any update on this?
get this merged, please!
@caiokf @jhsb25 working to ge this merged asap.