State file topic configs about kafka-gitops

[devshawn]

Hi @alex036, these are not showing as changes because they are considered broker defaults -- Confluent Cloud defaults to a cleanup.policy of delete and a retention time of 7 days, e.g. 604800000 ms.

So, when the tool looks for topic configs, it only looks for user-defined ones. Thus, the tool believes these configs have not been changed and ignores them. If you want to have the defaults explicitly defined as you have shown in your state file, you can just run an apply with the plan and it will put them in as a custom config. Confluent Cloud must not set custom configs if default values are provided. (I would do this with a test topic first to ensure nothing actually changes).

I tested out this scenario against a Confluent Cloud cluster and saw the same.

[alex036]

Hey @devshawn,
Appreciate the prompt reply.

I've been playing around with adding in other existing topics and I think I based most of my testing off of some test/unused topics that may have indeed been 100% default.

The other topics now have plans with the following as an example:

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update

The following actions will be performed:

Topics: 0 to create, 1 to update, 0 to delete.

~ [TOPIC] accounts_receivable
	~ configs:
		- cleanup.policy
		- min.insync.replicas
		- retention.ms
		- segment.ms


ACLs: 0 to create, 0 to update, 0 to delete.

Plan: 0 to create, 1 to update, 0 to delete.

Then I've just been adding in those custom configs to the state and re-planning to confirm the state and the cluster are the same state.

Thanks!