Kaustav Ghosh
09/26/2024, 11:20 AMuser
09/26/2024, 11:21 AMairbyte_cdk
folder in your local machine with the latest one from GitHub, or you can merge the latest master and that should take care of it. If you are working on python connectors, you may also need to reset the virtualenv
and re-install the connector's dependencies. Here is how you can do it: bash # Assuming you have a virtualenv loaded into your shell deactivate # From the connector's directory # remove the venv directory entirely rm -rf .venv # make and activate a new venv python3 -m venv .venv source .venv/bin/activate pip install -e ".[dev]"
Once you have successfully built the Platform images, you can load them into the abctl
Kind cluster, for example: bash kind load docker-image airbyte/server:dev --name airbyte-abctl
Then you can adjust your vaulues.yaml file to use the dev
tag for the component, e.g. yaml server: image: tag: dev
Then redeploy abctl
by running: bash abctl local install --values values.yaml
Please note that you don't necessarily have to delete and recreate the abctl docker container. You can simply update the image and redeploy. Sources: - [Forum Post: How to update CDK? > Answers Part 1](https://discuss.airbyte.io/t/768) - [Documentation > Contributing-to-airbyte > Developing Locally > Troubleshooting](https://docs.airbyte.com/contributing-to-airbyte/developing-locally#troubleshooting) - [Documentation > Contributing-to-airbyte > Developing Locally > Platform Contributions > Using the images in abctl](https://docs.airbyte.com/contributing-to-airbyte/developing-locally#using-the-images-in-abctl)