Provider produces invalid plan when removing dynamic "rule" blocks from autotag_v2

[mattBaumBeneva]

Describe the bug
We are currently migrating some of our configurations from an old autotag_v2 to a newer module. The autotag_v2 config generates "rule" blocks dynamically (ex.: dynamic "rule" {...}) and the for_each arguments are based on lists.

The apply step fails with the following error:

12:13:40  │ Error: Given property 'valueNormalization' with value: '' violates the following constraint: Value must be one of [Leave text as-is, To upper case, To lower case].
12:13:40  │ Given property 'type' with value: '' violates the following constraint: Value must be one of [ME, SELECTOR].
12:13:40  │ 
12:13:40  │   with dynatrace_autotag_v2.globale-proprietaire,
12:13:40  │   on TAG_globale-proprietaire.tf line 55, in resource "dynatrace_autotag_v2" "globale-proprietaire":
12:13:40  │   55: resource "dynatrace_autotag_v2" "globale-proprietaire" {

It seems thet the provider is generating an invalid plan for this ressource, which contains the following block:

12:13:14            + rule {
12:13:14              }

This obviously fails, because "valueNormalization" is required, as are other fields.

Expected behavior
It should be possible to remove any number of dynamically created "rule" blocks. It should also be possible to eventually destroy the entire old "autotag_v2" object.

Additional context
Provider version 1.46.1

[Dynatrace-Reinhard-Pilz]

Hello @mattBaumBeneva,

The symptoms sound awfully familiar like a bug within the plugin sdk we've already encountered. It happens - although not consistently - with nested schemas that contain unordered lists.

We've been successful with working around that bug in other resources. Unless this is something slightly different, the upcoming release will take care of it.

[Dynatrace-Reinhard-Pilz]

The changes will be available with the release tomorrow.
Just to be a bit more specific: You WILL still see the blocks like

12:13:14            + rule {
12:13:14              }

within the plan. It's not possible to prevent Terraform from creating them. But the Provider is able to recognize (and therefore ignore) them.