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
If you create a check in Icinga director using umlauts for example ü in the parameters the parameter is executed as ü
The services.conf file contains the ü but in the execution the ü is rendered as ü
To Reproduce
Use Check command
try in powershell: Invoke-IcingaCustomCheck -FileNames "für.txt"
[OK]
Add command using servicetemplate and set parameter
icinga renders C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -C "try { Use-Icinga -Minimal; } catch { Write-Output 'The Icinga PowerShell Framework is either not installed on the system or not configured properly. Please check https://icinga.com/docs/windows for further details'; Write-Output "Error: $($_.Exception.Message)Components:rn$( Get-Module -ListAvailable "icinga-powershell-*" )rnModule-Path:rn$($Env:PSModulePath)"; exit 3; }; Exit-IcingaExecutePlugin -Command 'Invoke-IcingaCustomCheck' " -FileNames 'für.txt'
and my check cant find the file because the name is wrong.
Expected behavior
render umlauts in command line
Your Environment
Include as many relevant details about the environment you experienced the problem in
Windows Server 2016
Icinga 2.12.5 server and client
powershell framework 1.5.0
should I convert the parameter in my powershell script?
thanks in advance
The text was updated successfully, but these errors were encountered:
Describe the bug
If you create a check in Icinga director using umlauts for example ü in the parameters the parameter is executed as ü
The services.conf file contains the ü but in the execution the ü is rendered as ü
To Reproduce
[OK]
r
n$( Get-Module -ListAvailable "icinga-powershell-*" )r
nModule-Path:r
n$($Env:PSModulePath)"; exit 3; }; Exit-IcingaExecutePlugin -Command 'Invoke-IcingaCustomCheck' " -FileNames 'für.txt'Expected behavior
render umlauts in command line
Your Environment
Include as many relevant details about the environment you experienced the problem in
Windows Server 2016
Icinga 2.12.5 server and client
powershell framework 1.5.0
should I convert the parameter in my powershell script?
thanks in advance
The text was updated successfully, but these errors were encountered: