You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is rather annoying, because it means my configurations for those old topics will have to include a long list of default values, values that I prefer not maintaining explicitly when it is something I have no specific preference for.
And it makes my configurations much longer, and less intuitive which settings have a reason for being there. I have to maintain all these settings which there is no reason for, which developers won't know by just looking at it. I can add comments, but its still much more verbose and harder to get an overview of which settings matter.
It would be much preferable if it was possible to simply remove the setting and let it be "unset" and fall back to the defaults that are managed by Confluent Cloud, rather than me needing to maintain my own copy of those default values.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue, @emilcn! It appears to be a duplicate of this issue. It’s currently blocked by the backend. The internal ticket key for this backend issue is KBROKER-389.
semaphore-agent-productionbot
changed the title
Reset to topic setting's default value operation is not supported
CLI-3482: Reset to topic setting's default value operation is not supported
Mar 18, 2025
I tried to remove topic settings that I no longer need, where I want to just fall back to whatever are the defaults provided by Confluent.
E.g. in below code I would remove some of the settings in the config block
I used provider version confluentinc/confluent v2.17.0
Upon removing those settings, I get this error:
This is rather annoying, because it means my configurations for those old topics will have to include a long list of default values, values that I prefer not maintaining explicitly when it is something I have no specific preference for.
And it makes my configurations much longer, and less intuitive which settings have a reason for being there. I have to maintain all these settings which there is no reason for, which developers won't know by just looking at it. I can add comments, but its still much more verbose and harder to get an overview of which settings matter.
It would be much preferable if it was possible to simply remove the setting and let it be "unset" and fall back to the defaults that are managed by Confluent Cloud, rather than me needing to maintain my own copy of those default values.
The text was updated successfully, but these errors were encountered: