@kapa.ai for the terraform provider im getting

╵ ╷ │ Error: failure to invoke API │  │  with airbyte_workspace.ozone, │  on <http://step1.tf|step1.tf> line 38, in resource "airbyte_workspace" "ozone": │  38: resource "airbyte_workspace" "ozone" { │  │ failed to get token: failed to decode token response: invalid character '<' │ looking for beginning of value ╵

this is after i set the provider version1.0.0-rc8 what is the problem,i've set the provider config correctly, it worked perfectly before

The error message

failed to get token: failed to decode token response: invalid character '<' looking for beginning of value

typically indicates that the token endpoint is returning an HTML response (like an error page) instead of a valid JSON token response. This usually points to a misconfiguration of the

server_url

or

token_url

in your provider setup. Based on the knowledge sources, here's what to check: Provider configuration — Make sure your provider block is correctly configured. For a self-managed instance, you need to explicitly set the

server_url

and ensure it points to the correct API endpoint: [Provider reference]

terraform {
  required_providers {
    airbyte = {
      source  = "airbytehq/airbyte"
      version = "1.0.0-rc8"
    }
  }
}

provider "airbyte" {
  client_id     = var.client_id
  client_secret = var.client_secret
  server_url    = "http://<YOUR_AIRBYTE_URL>/api/public/v1/"  # for self-managed
  # or omit server_url for Airbyte Cloud (defaults to https://api.airbyte.com/v1)
}

Things to verify: 1.

server_url

— If you're running Airbyte locally or self-managed, ensure the

server_url

is correct (e.g.,

http://localhost:8000/api/public/v1/

). If it's pointing to a wrong URL, the server may return an HTML error page instead of JSON. 2.

token_url

— The provider also accepts a

token_url

parameter. If your token endpoint differs from the default, you may need to set this explicitly. 3. Version-specific token issue — There is a known issue with token generation in certain Airbyte versions. One community report noted that a token generation issue was fixed in

v1.8.3

of Airbyte (self-managed). [token issue] If you recently upgraded Airbyte itself, this could be a factor. The knowledge sources do not contain specific details about breaking changes introduced in provider version

1.0.0-rc8

that would explain why it stopped working after an upgrade. I'd recommend checking the Terraform provider GitHub issues for any reported regressions in

rc8

, or temporarily pinning back to the last known working version to confirm the issue is version-specific. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I can generate my self a token here https://airbyte.preprod.apihub.openfinance.ae/api/v1/applications/token what is the problem then ?

The fact that you can successfully generate a token at

/api/v1/applications/token

but the Terraform provider is failing suggests a URL mismatch between where the provider is trying to fetch the token and where your token endpoint actually lives. Notice the difference in paths: • Your working token endpoint:

https://airbyte.preprod.apihub.openfinance.ae/api/v1/applications/token

• The self-managed token endpoint the provider expects by default: YOUR_AIRBYTE_URL`/api/public/v1/applications/token` The provider may be constructing the token URL incorrectly based on your

server_url

. You can explicitly override this by setting the

token_url

parameter in your provider configuration: [Provider reference]

provider "airbyte" {
  client_id     = var.client_id
  client_secret = var.client_secret
  server_url    = "https://airbyte.preprod.apihub.openfinance.ae/api/public/v1"
  token_url     = "https://airbyte.preprod.apihub.openfinance.ae/api/v1/applications/token"
}

The

token_url

is an explicit provider schema option that lets you point the provider to the correct token endpoint. [Provider reference] Try setting it to the URL where you can successfully generate tokens and see if that resolves the error. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.