NotificationCommand definition with env{} migrate to Icinga Director

[moreamazingnick]

Icinga Director can’t use env vars.

You can use the command natively in icinga and import it using director kickstarter.
The imported command can be used in icingadirector as external command but is not editable.

here is a post about env vars, I think this is natively used and imported:

Env variables are being taken in count?

I’m trying to use a telegram notification script I found here (GitHub - TeraIT-at/icinga-telegram-bot: Telegram Bot for Icinga2) For the notification definition it uses env variables and it’s defined as follows: object NotificationCommand "telegram-host-notification" { import "plugin-notification-command" command = [ SysconfDir + "/icinga2/scripts/telegram-host-notification.sh" ] env = { NOTIFICATIONTYPE = "$notification.type$" HOSTNAME = "$host.name$" HOSTALIAS = "$host.di…

and here is a hacky workaround:

Rocket.Chat notification help

try to run the go command manually (from shell) first, so we can exclude any configuration issues on the rocketchat side