-
Notifications
You must be signed in to change notification settings - Fork 31
Closed
Description
Expected Behavior
When I use a commandlet I expect the shell prompt to stay.
Current Behavior
Install-IcingaComponent is setting the shell prompt to C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins afterwards.
Uninstall-IcingaComponent is setting the shell prompt to C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-framework afterwards.
PS C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins> cd c:\
PS C:\> Install-IcingaComponent `
>> -Name 'plugins' `
>> -Version '1.10.0' `
>> -Confirm `
>> -Force;
[Notice]: Downloading "plugins" from "C:/ifw/icinga_stable/plugins/icinga-powershell-plugins-1.10.0.zip"
[Notice]: Installing version "1.10.0" of component "plugins"
[Notice]: Unblocking Icinga PowerShell Files
[Notice]: Installation of component "plugins" with version "1.10.0" was successful. Open a new PowerShell to apply the changes
PS C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins> cd c:\
PS C:\> Uninstall-IcingaComponent `
>> -Name 'plugins' `
>> -RemovePackageFiles;
[Notice]: Uninstalling Icinga for Windows component "icinga-powershell-plugins" from "C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins"
[Notice]: Successfully removed Icinga for Windows component "icinga-powershell-plugins" from "C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins"
True
PS C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-framework>
Possible Solution
You could save and restore the location of the shell prompt with something like:
$old-dir = get-location and set-socation $old-dir
Your Environment
icinga for windows with latest modules
Metadata
Metadata
Assignees
Labels
BugThere is an issue presentThere is an issue present