Terraform Provider Conflict When Primary Key Is Defined by Source

[bmschow]

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

│ key for stream: plans is already pre-defined. Please do NOT include a
│ primary key configuration for this stream

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:

│ airbyte_connection.massdriver_workfront_teams_to_redshift, provider
│ "provider[\"registry.terraform.io/airbytehq/airbyte\"]" produced an
│ unexpected new value: .configurations.streams[0].primary_key: new element 0
│ has appeared.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

[adam-bloom]

Appears to be a duplicate of #70

[bmschow]

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.