Consistent use of ENABLE in boolean environment variables
General
Escalation
General
Escalation
Description
How to test
List of changes
How to document
Double check Online help and env var for v3 - it should march.
Victoria metrics envvars link exists.
Smart Checklist
hideActivity
Show:
Done
Details
Details
Assignee

Reporter

Priority
Components
Needs QA
No
Needs Doc
No
Planned Version/s
Fix versions
Story Points
5.5
Smart Checklist Progress
1/1 - Done
Parent
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created May 1, 2024 at 8:46 AM
Updated December 2, 2024 at 3:05 PM
Resolved May 29, 2024 at 9:42 AM
Now that we have have achieved consistency by using PMM_ prefix in PMM env variables ( ) and removed dual booleans from our API ( ) we also want to use the word “ENABLE“ for the boolean variable.
Currently, we use both “ENABLE” and “DISABLE” in boolean env variable naming, which makes it challenging to remember which is should be used without consulting PMM documentation.
Therefore, we want to rename all mentions of “DISABLE” to “ENABLE” and reverse the logic as appropriate.