@kapa.ai Error: Provider produced invalid plan Provider "registry.terraform.io/airbytehq/airbyte" planned an invalid value for airbyte_connection.oracle_fusion_fscm_databricks_sync.configurations.streams: count in plan (cty.UnknownVal(cty.Number)) disagrees with count in config (cty.NumberIntVal(5)). This is a bug in the provider, which should be reported in the provider's own issue tracker.

The knowledge sources don’t mention this specific

count in plan ... disagrees with count in config

error for

airbyte_connection.configurations.streams

, so I can’t confirm an exact root cause or workaround from documentation. What is documented: •

configurations.streams

is an attribute set of stream objects; there is no documented

count

argument on

airbyte_connection

or on

configurations.streams

itself.[connection schema] • Similar provider-side bugs have occurred before (e.g.,

data_residency

enum casing, sync mode enum support) and were resolved only by upgrading to a newer provider version.[data_residency issue; sync mode issue] Given that: 1. The error text explicitly says “This is a bug in the provider”. 2. There is no documented

count

field on

streams

that you should or can control. 3. Prior similar issues were fixed in newer provider versions. The only actions I can confidently recommend based on the sources are: 1. Confirm you’re on the latest Airbyte Terraform provider (≥ 1.0) as shown in the getting started docs, e.g.:terraform { required_providers { airbyte = { source = "airbytehq/airbyte" version = "~> 1.0" } } }[Getting started] 2. If the error persists on the latest version, open an issue in the Airbyte Terraform provider tracker, including: ◦ Your provider version ◦ The

airbyte_connection

resource snippet (especially the

configurations

/

streams

block) ◦ The full error message The knowledge sources don’t provide a documented configuration change that would reliably avoid this specific

count

mismatch, so beyond upgrading and reporting it as a provider bug, I can’t suggest a guaranteed workaround. 👍 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 this is happening while setting up more than one streams. works when i add a single stream

The knowledge sources don’t describe this specific “count in plan … disagrees with count in config” bug when

configurations.streams

has more than one stream, so I can’t give a documented root cause or config-based fix. From the docs,

configurations.streams

is an attribute set of stream objects; there is no

count

argument you control there.[streams schema] The error message itself says this is a provider bug, and similar provider issues (e.g.,

data_residency

enum, sync mode enums) were only resolved by upgrading the provider.[data_residency issue; sync mode issue] Given that: 1. Upgrade to the latest provider (1.x series) if you haven’t already:terraform { required_providers { airbyte = { source = "airbytehq/airbyte" version = "~> 1.0" } } }[Getting started] 2. If it still fails only when you add multiple streams, this strongly suggests a bug in how the provider handles the

streams

set. In that case, the next step—per the error text—is to open an issue in the Airbyte Terraform provider tracker, including: ◦ Provider version ◦ Your full

airbyte_connection

resource (especially the

configurations = { streams = [...] }

block with multiple streams) ◦ The exact error message The knowledge sources don’t document any supported workaround (like a different syntax for multiple streams), so beyond upgrading and reporting, I can’t point to a reliable configuration change that will fix it. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.