Connector development on Windows #13674
Labels
area/documentation
Improvements or additions to documentation
autoteam
CDK
Connector Development Kit
community
team/documentation
type/enhancement
New feature or request
Update the documentation to make development of connectors on Windows easier
Hi team,
First of all, credits to where the Airbyte product is so far! 馃帀
This week I went through the process of creating an Airbyte Source connector on a Windows PC (It's what our company works with 馃槈). I would like to report the things I have found and how the process could be improved for other people who go through a similar workflow. I'm willing to submit PRs for the documentation and Airbyte itself, but as it is the first time I contribute to an open-source project, I need some guidance on whether it will be helpful for Airbyte or not. Thanks!
Things I've found:
1. Documentation about developing a Python Source is complete, but scattered
The documentation to develop a Python Source is complete, but as there are multiple pages with different approaches, it can be confusing for a newcomer (at least within my team). I know that the process around building a connector is evolving, but I think more consistency would help to improve the Developer Experience.
Examples that could use more consistency:
2. Code generation scripts are tailored towards Unix
All scripts for generating Python boilerplate code are heavily geared towards Unix. I can reverse engineer the proposed working of a Bash script myself, so I can run it in Powershell or CMD, but maybe the process could be changed so it works for all platforms (or add steps to the documentation, I'm not sure what has priority in your opnion)
The steps I have taken to make it work:
npm install
andnpm run generate
(Docker will also be possible, using the command ingenerate.sh
, but this one is easier for me)python -m venv .venv
.venv/Scripts/activate
to activate the virtual environment.python -m pip install -r requirements.txt
source-acceptance-test
plugin by navigating to this folder with the virtual environment still activated and runpython setup.py install
pip install '.[tests]'
3. Bugs in
source-acceptance-test
Pytest plugin when running on WindowsWhen you want to run the source acceptance tests on Windows, I was only able to get it working within the virtual environment (not in Docker, but unsure why).
In order to make the tests work in the virtual environment, I had to change to following things:
streams_without_records = streams_without_records - set(allowed_empty_streams)
run(["mkdir", "-p", LOG_DIR], shell=True)
.pip uninstall pytest-sugar
)It has become a bit longer than expected 馃槢 . So if I need to split it into multiple issues, just let me know!
Thanks!
The text was updated successfully, but these errors were encountered: