confluentinc / terraform-provider-confluent

Terraform Provider for Confluent
Apache License 2.0
27 stars 63 forks source link

Error creating Business Metadata Binding: Business-metadata attribute already exists in entity #362

Closed kaat-nnit closed 3 months ago

kaat-nnit commented 7 months ago

After evolving a schema which had business_metadata_binding added to a previous version, in the subsequent run to update tags and business metadata, terraform outputs the plan:

resource "confluent_business_metadata_binding" "business_metadata_binding" {
      ~ entity_name            = (sensitive value) # forces replacement
      ~ id                     = "*/test_pipeline_2/*:.:100280/sr_schema" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

And in the apply step the following error occurs:

Error: error creating Business Metadata Binding "*/test_pipeline_2/*:.:100281/sr_schema": Business-metadata attribute already exists in entity: *:.:100281.

This looks like the same problem with tag_binding resource which has been addressed in the following release: https://github.com/confluentinc/terraform-provider-confluent/releases/tag/v1.60.0 (Fixed "instance lsrc-abc123:.:100002 already is associated with classification dynamic" issue when updating confluent_tag_binding [resource])

Is it possible to have the same behaviour of the business_metadata_binding, such that the entity_name update is supported on the resource?

linouk23 commented 3 months ago

@kaat-nnit, we deployed a fix for this issue in our latest 1.77.0 release of the TF Provider 🫡.