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:
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?
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: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 theentity_name
update is supported on the resource?