You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the agent and proxy config templates - we have the following snippet which has been deprecated for some time:
### Option: EnableRemoteCommands - Deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead
# Internal alias for AllowKey/DenyKey parameters depending on value:
# 0 - DenyKey=system.run[*]
# 1 - AllowKey=system.run[*]
#
# Mandatory: no
EnableRemoteCommands=<%= @enableremotecommands %>
we should probably remove it in favour of replacing with an appropriate AllowKey or DenyKey configuration based on inputs which is already avaiable as config options in the module
i guess this needs a new major version of the module as such a change is potentially not backwards compatible although it would be fairly simple to create some logic to replicate what the zabbix config is doing transparently at this time.
The text was updated successfully, but these errors were encountered:
anthonysomerset
changed the title
EnableRemoteCommands is deprecated since v5.0.2 but we still deploy this config
EnableRemoteCommands is deprecated since Zabbix v5.0.2 but we still deploy this config
Jan 29, 2025
In the agent and proxy config templates - we have the following snippet which has been deprecated for some time:
we should probably remove it in favour of replacing with an appropriate AllowKey or DenyKey configuration based on inputs which is already avaiable as config options in the module
i guess this needs a new major version of the module as such a change is potentially not backwards compatible although it would be fairly simple to create some logic to replicate what the zabbix config is doing transparently at this time.
The text was updated successfully, but these errors were encountered: