Streams order changed between terraform plan and apply

[Jrmyy]

👋🏻 Hello

I am seing a strange behaviour in the terraform provider. A connection which is not updated will appear in the state (terraform plan) as modified because the streams list order can change over time.

This is problematic because we discard fields we don't want to synchronize to our destination but when terraform applies the change on the connection, it will reset the fields selection, which is far from ideal.

Is there a way to ensure consistency of streams order ?

[Jrmyy]

👋🏻 Hello
I can see that a new release 0.4.2 has been made. Is this release contains the fix to this issue ?

[Lau-ie]

I'm also getting this weird behaviour.

Terrafrom plan lists that a lot of connections will be updated in-place where only the order of the streams changes. When I try to apply anyway I run into Issue 91 where it errors out because it thinks there is a primary key configured.