We're using any as a type in multiple places to parse the Runtime Configuration of the checks. Since we're not actually using such a feature, we should move away from using the any interface. It complicates our code and makes parsing configuration for Checks prone to errors.
Solution Description
Use a RuntimeConfiguration struct to handle the configuration for all checks (as done now) and also use this in all places where the RuntimeConfiguration is touched upon (like the reconciling of the config itself), so we use something that's as close to universal as possible.
This object will be passed around and the per-check Config can be used in the needed places, with functions like GetHealthConfig().
I've refactored our current codebase to use some interfaces to handle Runtime Check configuration and remove the wild any usages here. We can come to this implementation or try some other once we've implemented the new Checks.
Is there an existing feature request for this?
Problem Description
We're using
any
as a type in multiple places to parse the Runtime Configuration of the checks. Since we're not actually using such a feature, we should move away from using the any interface. It complicates our code and makes parsing configuration for Checks prone to errors.Solution Description
Who can address the issue?
No response
Additional Context
No response