@kapa.ai I use Airbyte OSS with run-ab-platform.sh. Now that it is deprecated, how do I migrate to Airbyte newest version without losing all my config

To upgrade your local installation of Airbyte OSS to the latest version, you can use the

abctl

command line tool. Here are the steps: 1. Run

abctl local install

to upgrade to the latest version of Airbyte. 2. To ensure you're running the latest version of Airbyte, you can check the value of the Helm Chart's app version by running

abctl local status

. Please note that occasionally,

abctl

itself will need to be updated. You can do that by running

brew update abctl

. This is separate from upgrading Airbyte and only upgrades the command line tool. As for migrating your current config (sources, destinations, connections, stream states, etc) to the new deployment, you can export and import the complete configuration from one instance to another. The only requirement is both instances must have the same version. Please note that the

run-ab-platform.sh

script is deprecated and you should migrate to use

abctl

. For more information, you can check the [official documentation](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart). Sources: - [Upgrading Airbyte with abctl](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-with-abctl) - [Migrate Airbyte config from one deployment to another (OSS)](https://discuss.airbyte.io/t/370) - [Getting Started with Airbyte](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart)

@kapa.ai Airbyte upgrading worked well, but I lost all my sources, destinations and connections. How do I restore all these?

A message from kapa.ai

I'm sorry to hear that you've lost your sources, destinations, and connections. To restore these, you'll need to have exported your configuration data prior to the upgrade. If you have an export of your configuration data, you can import it back into Airbyte. Here are the steps to import your configuration data: 1. Navigate to the Admin page in the Airbyte UI. 2. Click on "Import / Export". 3. In the Import section, click on "Upload File" and select your configuration data file. 4. Click on "Import Data". Please note that the import operation will overwrite any existing configuration data. Make sure that the Airbyte version of the data you are trying to import is the same as the one running in your Airbyte instance. If you didn't export your configuration data before the upgrade, unfortunately, there's no way to recover your sources, destinations, and connections. You'll need to manually recreate them. For future reference, it's recommended to regularly export your configuration data, especially before performing an upgrade. This provides a backup that can be used to restore your configuration in case something goes wrong. For more information on exporting and importing data in Airbyte, see [this page](https://docs.airbyte.com/operator-guides/importing-and-exporting-data).

@kapa.ai I could restore a docker compose version. So now I work on a docker compose version. When I try to create a source I have the following message: Failure origin: airbyte_platform

A message from kapa.ai

The error message "Failure origin: airbyte_platform" is quite generic and could be caused by a variety of issues. It's hard to provide a specific solution without more details about the error. However, here are a few general troubleshooting steps you can try: 1. Check the logs: You can view the logs in the Airbyte UI under the "Logs" tab. This might give you more information about what's causing the error. 2. Check your Airbyte version: Make sure you're running the latest version of Airbyte. You can check your current version in the lower left corner of the Airbyte UI. If you're not on the latest version, consider upgrading. 3. Check your source configuration: Make sure the configuration for the source you're trying to create is correct. This includes things like credentials, URLs, etc. 4. Check your network connection: Make sure your Airbyte instance has a stable internet connection and can reach the source you're trying to connect to. If none of these steps help, I would recommend creating a new post on the [Airbyte Github Discussions](https://github.com/airbytehq/airbyte/discussions) or [Airbyte Community Forum](https://discuss.airbyte.io/) with more details about your issue. The Airbyte community and team are usually very responsive and can help troubleshoot further.

@kapa.ai here are the logs: io.temporal.failure.ActivityFailure: Activity with activityType='RunWithJobOutput' failed: 'Activity task failed'. scheduledEventId=12, startedEventId=13, activityId=59651b1e-d06f-376a-8370-0a6ca40bf341, identity='1@d8eafbf7c27e', retryState=RETRY_STATE_MAXIMUM_ATTEMPTS_REACHED at java.base/java.lang.Thread.getStackTrace(Thread.java:2450) at io.temporal.internal.sync.ActivityStubBase.execute(ActivityStubBase.java:49) at io.temporal.internal.sync.ActivityInvocationHandler.lambda$getActivityFunc$0(ActivityInvocationHandler.java:83) at io.temporal.internal.sync.ActivityInvocationHandlerBase.invoke(ActivityInvocationHandlerBase.java:60) at jdk.proxy2/jdk.proxy2.$Proxy107.runWithJobOutput(Unknown Source) at io.airbyte.workers.temporal.check.connection.CheckConnectionWorkflowImpl.run(CheckConnectionWorkflowImpl.java:55) at CheckConnectionWorkflowImplProxy.run$accessor$3mn7EjRK(Unknown Source) at CheckConnectionWorkflowImplProxy$auxiliary$E6TAZDpy.call(Unknown Source) at io.airbyte.micronaut.temporal.TemporalActivityStubInterceptor.execute(TemporalActivityStubInterceptor.java:79) at CheckConnectionWorkflowImplProxy.run(Unknown Source) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at io.temporal.internal.sync.POJOWorkflowImplementationFactory$POJOWorkflowImplementation$RootWorkflowInboundCallsInterceptor.execute(POJOWorkflowImplementationFactory.java:339) at io.temporal.internal.sync.POJOWorkflowImplementationFactory$POJOWorkflowImplementation.execute(POJOWorkflowImplementationFactory.java:314) at io.temporal.internal.sync.WorkflowExecutionHandler.runWorkflowMethod(WorkflowExecutionHandler.java:70) at io.temporal.internal.sync.SyncWorkflow.lambda$start$0(SyncWorkflow.java:135) at io.temporal.internal.sync.CancellationScopeImpl.run(CancellationScopeImpl.java:102) at io.temporal.internal.sync.WorkflowThreadImpl$RunnableWrapper.run(WorkflowThreadImpl.java:107) at io.temporal.worker.ActiveThreadReportingExecutor.lambda$submit$0(ActiveThreadReportingExecutor.java:53) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)

A message from kapa.ai

The error message you're seeing is related to Temporal, the workflow orchestration platform that Airbyte uses. The error message

ActivityFailure: Activity with activityType='RunWithJobOutput' failed: 'Activity task failed'

indicates that a Temporal activity failed. However, the logs you've provided don't give specific details about what caused the activity to fail. It could be due to a variety of reasons such as network issues, incorrect configuration, or an issue with the source connector. Here are a few steps you can take to troubleshoot this issue: 1. Check the source configuration: Make sure the configuration for the source you're trying to create is correct. This includes things like credentials, URLs, etc. 2. Check your network connection: Make sure your Airbyte instance has a stable internet connection and can reach the source you're trying to connect to. 3. Try a different source: If possible, try creating a different source to see if the issue is specific to the source you're trying to create. 4. Check for known issues: Search the [Airbyte Github Issues](https://github.com/airbytehq/airbyte/issues) to see if there are any known issues related to the source you're trying to create. If none of these steps help, I would recommend creating a new issue on the [Airbyte Github Issues](https://github.com/airbytehq/airbyte/issues) with more details about your issue. Include the full logs and details about the source you're trying to create. The Airbyte team can help troubleshoot further.