Open bmschow opened 6 months ago
Appears to be a duplicate of https://github.com/airbytehq/terraform-provider-airbyte/issues/70
just confirmed that this bug does not happen on an initial create
but happens only on a modify
. I can reproduce it when i initially make a connection with no primary key specified and then try to modify the status
field.
When I use terraform and try to specify a primary key in a stream for a postgres connection with a sync type of incremental_dedup_history i get
however, if i do not specify a primary key it tells me I must specify a primary key. I can get past this by specifying: "primary_key": [] however, this still gives a terraform error: