Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EnableRemoteCommands is deprecated since Zabbix v5.0.2 but we still deploy this config #983

Open
anthonysomerset opened this issue Jan 29, 2025 · 0 comments

Comments

@anthonysomerset
Copy link
Contributor

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.

@anthonysomerset 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant