bug: config map enabled elements is not properly scoped

[razbroc]

in case of tracing.enabled set to false, it won't be set to false in configmap - and be undefined instead

[shimoncohen]

As mentioned here:
https://github.com/MapColonies/telemetry?tab=readme-ov-file#tracing-configuration

The valid values are true and false, but in case of undefined the env value would be removed as such:
https://github.com/MapColonies/telemetry/blob/a09788899eb40945ce79632f2ca516a6d7626c3d/src/common/config.ts#L44-L48

Have you run in to an issue where the undefined value was actually passed? If not, I think this issue can be closed.

[razbroc]

the problem is that the env would be removed. people tend to query this value in their code and expect to get true or false , in this case they get undefined - querying a non-existent value.

[shimoncohen]

It's not a problem if you use our telemetry package.
As I mentioned before it sets the value to be false as default when the env is undefined.

[razbroc]

i need to check further, but i think the bug is caused because of out helm hierarchy, global is trying to run over the 'undfiend' value which causes the problem.

[shimoncohen]

@razbroc Can this issue be closed?