Hello everyone! I’m Jerri Comeau, the manager of the Community Assistance Team, and I’m here to tell you about some big changes coming to our current Github repository structure and processes. Executive summary: 1. The current repo, airbytehq/airbyte, is being separated into two repos to simplify the deployment process both internally and externally. 2. Connectors will continue to live in airbytehq/airbyte and

docker-compose up

will still work from this directory. 3. Platform code is being consolidated in the new airbytehq/airbyte-platform repo and users will need to switch to this repo to actually start and run Airbyte. Detailed Information: In order for our Engineering, Product, and Design teams to more quickly and efficiently deploy new code, we decided that the best thing to do was to split up our repositories into two already-existing pieces: the connector functionality and the platform/deployment functionality. This will allow us to make isolated changes discreetly and improve the development workflow. We’ll be making this change on 20 February but we’re letting you know now so you can prepare your workflows ahead of the change. We have done our best to limit the impact of this change, and we want everyone to know ahead of time what we’re doing. We’ll also be reminding you again before the rollout happens on 20 February.. We’ll also be updating our documentation and walkthroughs to make sure they reflect the change. Any questions? Please don’t hesitate to let us know.

Hi @Jerri Comeau (Airbyte), do you have a sample of the documentation after change?

Our engineering team in charge of the project is working very hard to make the change mostly transparent to users; we’ll be pushing out a new official Helm Chart that takes the repo changes into account around the same time. We should have documentation ASAP ; we’ll share it as soon as we have a readable version.

@Jerri Comeau (Airbyte) are there any actions we should perform if we run standard Airbyte on Compute Engine? Airbyte is implemented using these docs https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine/

Just a quick note to say that Phase 1 of the Monorepo change is complete and most of the unforseen issues have been dealt with. The rest of the changes in Phase 2 should be internal-only, and shouldn’t impact the community at all. Thank you for your patience and attention!

Hi! The helm charts are not getting published - most probably due to the name of the default branch in the new repo - use main instead of master https://github.com/airbytehq/airbyte-platform/blob/main/.github/workflows/publish-helm-charts.yml#L1-L8