-
Notifications
You must be signed in to change notification settings - Fork 204
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
Unable to use constants in templates or commands #1075
Comments
This also hurts me when I want to define a commandline like |
@dgoetz Absolute paths are accepted as provided, relative paths are prefixed with "PluginDir + ", similar Constant prefixes are allowed. If you use the full path it won't add |
@cflinspach: Thanks, but the problem is that I need PluginDir because of the different os families used here. |
@dgoetz so |
@cflinspach: Yes, SLES uses arch-independent /usr/lib/nagios/plugins and RHEL uses arch-dependent /usr/lib64/nagios/plugins. |
+1 for use of Constants. Big problem with secure information. Now usernames/passwords has to be in the DB - not good. |
+1 :) I think a rather easy solution would be to add some special syntax like {{{mystring}}} to avoid that the director placing quotes around that "string". In my case i need that for auto creating the display_name:
Never found a way to configure this with the director. |
ref/NC/589957 |
Is there any news on this issue? Or is there another way of supporting different plugin directories on different operating systems? |
Hi @Linuxfabrik, that's perfectly possible, has been fixed a long time ago. You can use @cflinspach showed how to use In case you really need a solution for that specific use-case please open a dedicated issue. I'll close this one for now - as what has originally been asked for has been implemented. Cheers, |
Director 1.3.1
When I use constants in commands or command templates the constants always get quoted and dont get expanded
When I edit the the conf file by hand and remove the quotes and reload icinga2 the constants get expanded.
The text was updated successfully, but these errors were encountered: