I am working on cleaning up our parameters, documenting and renaming some that are copies (e.g.
ntp-server). While working on this, it makes sense to find a common naming scheme and enforce it for once and forever probably via a simple Raketask (grep) or rule for https://github.com/Shopify/erb-lint. We have several styles, the purpose of this poll is to find the preferred way, then rename all parameters of course in non-breaking way (implementing aliases and auto conversion of existing ones) and enforce the style in our codebase.
ntp_server(67 params today)
The reason why we want to cleanup the list is user experience, we are going to show parameters on the host/hostgroup form, even if we improve the UI we don’t want to confuse users with showing two or three variants of the same parameter.
I’d prpopose to implement auto aliasing with deprecation warning, a simple hash hardcoded in the codebase converting renamed names to new one issuing deprecation warning. Also for user convinience, if we pick let’s say underscore, it would automatically convert
ntp-server issuing the same warning.
If you just want me to cleanup parameters, rename and deprecate old ones (without new “auto coversion”) or simply keep the status quo, drop a comment below. I cannot edit a poll anymore.