Open cpaelzer opened 1 year ago
Seconding the request! I came here to make the same suggestion after seeing it - would very much like to see the wording changed. allowlist
/denylist
are pretty standard go-to's for those.
Thanks!
Usually this is handled with aliases, although this is more than just the configuration format, since there may be downstream scripts or processes that parse output. I think it could be done with separate aliases for configuration and an option for output strings. For context, here's a good explanation on why blacklist/whitelist are problematic: https://www.splunk.com/en_us/blog/learn/blacklist-whitelist-inclusivity.html
It might not be possible to discontinue the old key names in the config too quickly, but unattended-upgrades still uses non inclusive naming like blacklist/whitelist in config, output and code. At least some could be tackled without incompatibilities with old config files I guess?
Example: