Summary
The user is facing an issue with the API used for the Terraform provider after starting to use abctl. They mentioned using Docker Compose version and providing username and password in the provider.
Question
Hi, after start using abctl the api I was using for terraform provider does not work anymore. I used docker compose version. I used username and password in the provider.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["abctl", "api", "terraform-provider", "docker-compose", "username-password"]
This is resolved by using /api/public/v1/ and the port is 8000. There’s no documentation about this change.
Also you need to use client_id, client_secret.
There are docs for that, but they are not easy to find
https://reference.airbyte.com/reference/standalone-server-deprecation-and-migration-to-airbyte-server
> OSS users using the airbyte-api-server need to migrate their API calls to reference the airbyte_server. If you were using the Airbyte API, you will have to update callers to point to airbyte-server/api/public as the base URL. Anything already pointing to the airbyte-server needs no change.
> For example, an API call localhost:8006/v1/workspaces must be migrated to: localhost:8001/api/public/v1/workspaces
https://reference.airbyte.com/reference/authentication#airbyte-oss-users
> Airbyte OSS Users
> If you use the Airbyte API in OSS, you can use the credentials set for your UI instance. To do this, you should use the Basic authentication, with the username and password separated by a colon and Base64 encoded