Terrajet should skip writing conflicting fields

[muvaf]

What problem are you facing?

When there are conflicting fields and we late initialize all of them, they all end up in our parameters and then terraform returns error after the first late-init saying there are conflicting fields, like "network_interface": conflicts with private_ip

How could Terrajet help solve your problem?

We could either skip late initialization of such fields or make the FileProducer smarter by adding logic to not write conflicting fields into the main.tf.json but that could be challenging since we don't know which fields are given by user and which of them are late-inited. Best solution could be to make terraform to skip conflict errors but I couldn't find a way to do that.

[muvaf]

It seems like there isn't a way other than forking Terraform to disable conflict checks https://github.com/hashicorp/terraform-plugin-sdk/blob/e91cd2e/helper/schema/schema.go#L1524

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.