how do I know which terraform provider version works with which version of airbyte oss

The knowledge sources do not explicitly document a compatibility matrix between specific Terraform provider versions and specific Airbyte OSS versions, so I can’t give an exact version‑to‑version mapping. What is documented: - The Terraform provider is built on top of the public Airbyte API, and the setup examples simply pin a provider version (e.g.

version = "0.6.5"

) without tying it to a particular Airbyte OSS release. [[Step 1 provider](https://docs.airbyte.com/developers/terraform-documentation#step-1-set-up-the-terraform-provider)] - There is a known class of issues where the provider and the connectors (and by extension the API) can drift: upgrading the provider without upgrading connectors, or upgrading connectors when the provider hasn’t been regenerated yet, can cause failures. [[Typing](https://docs.airbyte.com/developers/terraform-documentation#typing)] - The docs recommend using the weakly typed JSON resources (

airbyte_source_custom

,

airbyte_destination_custom

) specifically because they are more robust to mismatches between the Terraform provider and connector/API changes. [[Typing](https://docs.airbyte.com/developers/terraform-documentation#typing)] Given what’s available, the best documented guidance is: 1. Pin a provider version in Terraform (as in the examples) and keep it aligned with the Airbyte API you’re actually running; when you upgrade Airbyte OSS, test your Terraform workflows and upgrade the provider if needed. [[Step 1 provider](https://docs.airbyte.com/developers/terraform-documentation#step-1-set-up-the-terraform-provider)] 2. Prefer JSON (weakly typed) resources for sources/destinations to reduce breakage when provider and connectors/API are slightly out of sync. [[Typing](https://docs.airbyte.com/developers/terraform-documentation#typing)] If you need an exact compatibility matrix (e.g., “Airbyte OSS 1.XX ↔️ provider 0.YY”), that information is not present in the provided sources.