Problem
The current Helm chart defines boolean-like values as strings (e.g. "true" / "false"). In a development branch (kubernetes-ready-pgwatch), these have been changed to native YAML booleans (true / false), which is more consistent with Helm conventions.
Using native booleans simplifies template logic and reduces the risk of subtle type-related issues.
Proposal
Standardize all boolean-like values to use native boolean types (true / false) and update templates accordingly (e.g. replace string comparisons with direct boolean checks).
There may be existing users relying on string inputs. Even though the charts are not officially supported, this should still be considered. The change can be documented clearly, and if needed, temporary compatibility handling for both string and boolean inputs can be introduced.
Rationale
- Aligns with Helm/YAML best practices
- Improves readability and maintainability
- Reduces risk of type-related bugs (e.g. "false" mistakenly treated as
truthy)
Problem
The current Helm chart defines boolean-like values as strings (e.g.
"true"/"false"). In a development branch (kubernetes-ready-pgwatch), these have been changed to native YAML booleans (true/false), which is more consistent with Helm conventions.Using native booleans simplifies template logic and reduces the risk of subtle type-related issues.
Proposal
Standardize all boolean-like values to use native boolean types (
true/false) and update templates accordingly (e.g. replace string comparisons with direct boolean checks).There may be existing users relying on string inputs. Even though the charts are not officially supported, this should still be considered. The change can be documented clearly, and if needed, temporary compatibility handling for both string and boolean inputs can be introduced.
Rationale
truthy)