Anyone else having trouble using

airbyte_source_linear

in terraform? https://github.com/airbytehq/terraform-provider-airbyte/issues/213

Based on the knowledge sources provided, there is no direct mention of issues or troubleshooting steps specifically related to using the

airbyte_source_linear

resource in Terraform. The documentation does describe two approaches for managing Airbyte sources with Terraform: strongly typed resources (like

airbyte_source_linear

) and weakly typed (JSON-based) resources using

airbyte_source_custom

. Airbyte generally recommends using the JSON configuration approach for better compatibility and less drift, especially as connectors and the provider evolve independently. This method can be more robust if you encounter issues with strongly typed resources like `airbyte_source_linear`[Strongly typed vs weakly typed](https://docs.airbyte.com/platform/terraform-documentation#typing). If you are experiencing trouble with

airbyte_source_linear

, you might consider switching to the JSON-based approach with

airbyte_source_custom

and using the configuration JSON copied from the Airbyte UI. However, the knowledge sources do not provide specific troubleshooting steps or known issues for

airbyte_source_linear

. If you need further help, you may want to check the referenced GitHub issue or open a new one with details about your problem.

resource "airbyte_source_custom" "source" {
  name         = "tf_linear"
  workspace_id = var.workspace_id

  configuration = jsonencode({
    "api_key" = var.linear_api_key
  })

  definition_id = "1c5d8316-ed42-4473-8fbc-2626f03f070c" # Linear connector ID
}

managed a workaround