@rapid-van-91305 @astonishing-stone-14417 I am having multiple constant definitions with the same values like the following:

const (
	KernelDefaultsProtectionEnabled  KernelDefaultsProtectionPolicy = "enabled"
	KernelDefaultsProtectionDisabled KernelDefaultsProtectionPolicy = "disabled"
)

const (
	EtcdMetricsEnabled  EtcdMetricsExposurePolicy = "enabled"
	EtcdMetricsDisabled EtcdMetricsExposurePolicy = "disabled"
)

Is this overkill, or is it how it should be ?

Maybe if they have the same values i’d use just one type / constants

Most of these were

bool

that we changed to

Enum

for best practices, it looks like we would lose the benefit of the change if we do that. Am I wrong ?

I'm not strictly against bools but I've seen cases when they had to be expanded with other options.

In CAPA we don’t use Enums for bools

OK, let's say : if it is and should always be

enabled

or

disabled

, we would just put a

bool

Yes i would say so

OK, cool ... I don't think I can recover an old commit after so many commits in between, so I will just refactor