Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Checking upgrading docs, the process looks rather tricky and difficult to automate. Are there any plans to make configuration upgrade possible via UI / API?
Like
1. Export configuration
2. install fresh Airbyte version (or spin up a new VM)
3. Import the exported file back
4. Migration happens automatically
5. ??? PROFIT
I’ve made a `packer` script building a VM and switching to new Airbyte is a matter of 1 line change.

Also are there e2e examples of API calls for setting up connections?

yes, we are aware of the pain points in our upgrading process and discussing how/what to do about it

We have a few issues for example:
• <https://github.com/airbytehq/airbyte/issues/2595>
• <https://github.com/airbytehq/airbyte/issues/2598>
• and maybe more


&gt; Also are there e2e examples of API calls for setting up connections?
Not sure if we have proper documented API calls… I don’t think so, as we also have a disclaimer on API usage:

&gt;  Our Configuration API is still in alpha and might change. You won’t lose any functionality, but you may need to update your code to catch up to any backwards incompatible changes in the API.
&gt; *Check it out* *<https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html|here>.* It is still rudimentary, and we will improve in the next couple of weeks.
source: <https://docs.airbyte.io/api-documentation>

But we do have some tests written using the API here for our own use… so maybe you could have a look at these:
<https://github.com/airbytehq/airbyte/blob/master/airbyte-tests/src/acceptanceTests/java/io/airbyte/test/acceptance/AcceptanceTests.java>

Otherwise, you have related threads on slack of users trying things out too: <https://airbytehq.slack.com/archives/C019WJFR1JT/p1621330176006400>