airbyte-connectors
airbyte-connectors copied to clipboard
faros-ai
Airbyte connectors (sources & destinations) + Airbyte CDK for JavaScript/TypeScript
Tracking issue for: - [ ] https://github.com/faros-ai/airbyte-connectors/security/code-scanning/10
Spec.json points to Bitbucket Server docs for access tokens when it should be pointing to Bitbucket Cloud docs. It should also inform the user of the following: 1. Access tokens...
Either as `*` (all projects) or a list of projects `project1,project2`
Currently Azure Repos source fetches commits folded into repository objects. Instead, the branches & streams be split into two separate streams.
None of the current streams are incremental. We should make them so whenever possible.
I have changed something in the code of azure-repos-source locally on my machine and builded a docker image liked it is discribed here https://github.com/faros-ai/airbyte-connectors/tree/main/sources/azure-repos-source If I try to run this...
In [the Google Calendar Source README](https://github.com/faros-ai/airbyte-connectors/tree/main/sources/googlecalendar-source), there's this link to Airbyte's doc: https://docs.airbyte.io/integrations/sources/googlecalendar However it doesn't exist anymore. Where can we find more information about the Google Calendar Connector? Thank...
I created customer io source and also generated app api key from customer io account settings. I am able to access customer io apis from postman using that api key...
e.g. branches see https://github.com/faros-ai/airbyte-connectors/tree/main/destinations/airbyte-faros-destination/src/converters/bitbucket-server vs https://github.com/faros-ai/airbyte-connectors/tree/main/destinations/airbyte-faros-destination/src/converters/bitbucket
Our Harness connector only supports Harness [FirstGen](https://docs.harness.io/article/1fjmm4by22-harness-first-gen-vs-harness-next-gen). Harness NextGen has a [different](https://docs.harness.io/article/tm0w6rruqv-harness-api), REST-based API.