confluent_schema_exporter: automatically pause schema exporter for update

[S1M0NM]

The current implementation of the provider actively forces the user to pause the schema exporter to change the configuration. This is particularly inconvenient in build pipelines as it requires 2 commits and 2 executions. If the change is made via a pull request, a second pull request is also required.

It would be ideal if the provider would first pause the schema exporter during an update, then apply the changes to the configuration and finally start the exporter again.

[linouk23]

Thank you so much for reporting this issue @S1M0NM!

Also thanks for trying out _confluent_schemaexporter resource while it is still in Preview. Your feedback will help us to ensure a great user experience when _confluent_schemaexporter resource becomes Generally Available.

It would be ideal if the provider would first pause the schema exporter during an update, then apply the changes to the configuration and finally start the exporter again.

Just to clarify, are you suggesting that we remove the 'status' attribute and process pauses within TF Provider?

[S1M0NM]

I wouldn't necessarily remove the attribute in case you want to temporarily pause the exporter.

Otherwise it is correct that my suggestion includes that the TF provider takes care of pausing during updates.

[zhenli00]

It's on our road plan, we will add this enhancement in coming weeks! Thanks for providing the feedback.