Changing topic configuration generates a replace instead of an update

[confluentinc]

Changing topic configuration generates a replace instead of an update

[linouk23]

@moonsub-kim @gof-ctm @AnishJS @userkci @vpoyraz @jmborsani

I've got a quick question regarding this issue: will it be helpful to introduce topic config updates without allowing a user to delete a topic config at all (but supporting value updates"retention.ms" = "600000" -> "6000000" / adding new topic configs)? Please react either 👍 or 👎 .

[gof-ctm]

Am waiting for a resolve because if I change Topic name then it gets replaced not updated.

[linouk23]

@moonsub-kim unfortunately it doesn't.

[linouk23]

Thanks for creating this issue @userkci! We're going to address it (supporting in-place updates for topic configuration) in one of our future releases, stay tuned!

[AnishJS]

This seems critical and a basic requirement, when would it be available please?

[moonsub-kim]

Does v0.4.0 resolve this? @linouk23

[pbarsotti-glovo]

Also deletion is not a sync operation, so many times the creation fails with an error "Error: 400 Bad Request: Topic 'topic_name' is marked for deletion." since the provider is not waiting for the finalization before trying to recreate it.

[linouk23]

@pbarsotti-glovo interesting, you mean like topic deletion?

update: opened Make topic deletion a sync operation to track this issue, thanks for reporting it!

[linouk23]

Check out our most recent release of the TF Provider for Confluent Cloud v0.5.0 where we fixed the issue!

cc @pbarsotti-glovo @moonsub-kim @gof-ctm @AnishJS @userkci @vpoyraz @jmborsani @EaglelJoe