Closed Noel-Jones closed 6 months ago
We are also having this issue, it's preventing us from updating any existing topics using Terraform. This is definitely a bug versus an enhancement since it prevents you from updating any existing topics and the Error messages' fix also doesn't work.
@Noel-Jones, @shriman-desikan thanks for creating this PR!
Could you confirm you are interested in the following 2 topic settings:
log.message.timestamp.before.max.ms
log.message.timestamp.after.max.ms
Yes, those are the two topic settings that I guess should be editable going forward.
This all seems related to this KIP and Confluent's adoption of Kafka version 3.6.x, for more context.
Thank you!
Thanks!
We have internally merged a fix and are planning to release a new version of the TF Provider today or tomorrow, which will include this fix. Thank you for your patience!
@shriman-desikan @Noel-Jones
Update: we
Added a client side fix for "Add support for new topic configuration fields" issue (https://github.com/confluentinc/terraform-provider-confluent/issues/341).
in our latest 1.57.0 version of TF Provider.
Thanks for waiting and let us know if you run into any issues when using the latest 1.57.0 version of TF Provider.
Thank you, v1.57 does resolve this issue.
Following on from #339 I just got around to updating my code to set the fields message.timestamp.after.max.ms and message.timestamp.before.max.ms to the default values. Now I get the message
The provider needs to be updated to support setting of these fields. I am raising this as a new issue because it is a specific issue with a more significant impact that prevents me from being able to apply. If I set the config value I get the error shown above, if I don't set the field I get the error below!