Skip to content

Commit 8bed2b9

Browse files
authored
Merge pull request #692 from Icinga:feature/rename_ifw_service_restart_cmdlet
Feature: Renames "Restart-IcingaWindowsService" to "Restart-IcingaForWindows" and adds alias for backwards compatibility Renames `Restart-IcingaWindowsService` to `Restart-IcingaForWindows` and adds alias for backwards compatibility to start unifying the Icinga for Windows cmdlets
2 parents 05f16b3 + b5ffdd1 commit 8bed2b9

24 files changed

+30
-27
lines changed

doc/100-General/01-Upgrading.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Import-Module icinga-powershell-framework -Force;
2828
Import-Module icinga-powershell-framework -Global -Force;
2929
3030
# Restart the Icinga for Windows service in case installed, to ensure the functionality
31-
Restart-IcingaWindowsService;
31+
Restart-IcingaForWindows;
3232
3333
# Add your own update procedure code
3434
```

doc/100-General/10-Changelog.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ Released closed milestones can be found on [GitHub](https://github.com/Icinga/ic
2626
* [#679](https://github.com/Icinga/icinga-powershell-framework/pull/679) Adds a new data provider for fetching process information of Windows systems, while sorting all objects based on a process name and their process id
2727
* [#688](https://github.com/Icinga/icinga-powershell-framework/pull/688) Adds new handling to add scheduled tasks in Windows for interacting with Icinga for Windows core functionality as well as an auto renewal task for the Icinga for Windows certificate generation
2828
* [#690](https://github.com/Icinga/icinga-powershell-framework/pull/690) Adds automatic renewal of the `icingaforwindows.pfx` certificate for the REST-Api daemon in case the certificate is not yet present, valid or changed during the runtime of the daemon while also making the `icingaforwindows.pfx` mandatory for all installations, regardless of JEA being used or not
29+
* [#692](https://github.com/Icinga/icinga-powershell-framework/pull/692) Renames `Restart-IcingaWindowsService` to `Restart-IcingaForWindows` and adds alias for backwards compatibility to start unifying the Icinga for Windows cmdlets
2930

3031
## 1.11.2 (tbd)
3132

doc/100-General/20-Eventlog.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Below you will find a list of EventId's which are exported by this module. The s
8484

8585
| Category | Short Message | Detailed Message |
8686
| --- | --- | --- |
87-
| Error | Unable to start Icinga for Windows service | Unable to start Icinga for Windows service, as the JEA session created by the service is still active. Run "Restart-IcingaWindowsService" to restart the Icinga for Windows service, while running in JEA context to prevent this issue. |
87+
| Error | Unable to start Icinga for Windows service | Unable to start Icinga for Windows service, as the JEA session created by the service is still active. Run "Restart-IcingaForWindows" to restart the Icinga for Windows service, while running in JEA context to prevent this issue. |
8888

8989
## Event Id 1504
9090

doc/110-Installation/05-Background-Daemons.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,5 +77,5 @@ No arguments defined
7777
In order to apply any changes on background daemons, you will always to restart the Icinga for Windows PowerShell service. You can do so with the following command:
7878

7979
```powershell
80-
Restart-IcingaWindowsService;
80+
Restart-IcingaForWindows;
8181
```

doc/110-Installation/06-Collect-Metrics-over-Time.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,5 +122,5 @@ Unregister-IcingaServiceCheck -ServiceId 133219181168290951798237215145107197204
122122
Finally to apply all your changes, we have to restart the Icinga for Windows Powershell Daemon
123123

124124
```powershell
125-
Restart-IcingaWindowsService;
125+
Restart-IcingaForWindows;
126126
```

doc/110-Installation/30-API-Check-Forwarder.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Enable-IcingaFrameworkApiChecks;
7575
Last but not least restart the Icinga for Windows service:
7676

7777
```powershell
78-
Restart-IcingaWindowsService;
78+
Restart-IcingaForWindows;
7979
```
8080

8181
As long as the feature is enabled, the Icinga for Windows service is running and the REST-Api daemon is registered, checks will be forwarded to the REST-Api and executed, if whitelisted.
@@ -98,7 +98,7 @@ For quick installation, here the list of commands to get everything running:
9898
Register-IcingaBackgroundDaemon -Command 'Start-IcingaWindowsRESTApi';
9999
Add-IcingaRESTApiCommand -Command 'Invoke-IcingaCheck*' -Endpoint 'apichecks';
100100
101-
Restart-IcingaWindowsService;
101+
Restart-IcingaForWindows;
102102
103103
Enable-IcingaFrameworkApiChecks;
104104
```

doc/900-Developer-Guide/10-Custom-Daemons.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -301,7 +301,7 @@ Register-IcingaBackgroundDaemon -Command 'Start-IcingaAgentServiceTest';
301301
Once registered, you will have to restart the PowerShell service itself to apply the changes
302302

303303
```powershell
304-
Restart-IcingaWindowsService;
304+
Restart-IcingaForWindows;
305305
```
306306

307307
Thats it! Now the daemon is loaded with every start, checking for the Agent state and restart it if it is not running.

doc/900-Developer-Guide/12-Custom-API-Endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,7 +237,7 @@ If our module is providing different endpoints, you will have to create multiple
237237
As everything is now ready, we can restart our Icinga PowerShell Framework service by using
238238

239239
```powershell
240-
Restart-IcingaWindowsService;
240+
Restart-IcingaForWindows;
241241
```
242242

243243
and access our API endpoint by browsing to our API location (in our example we assume you use `5668` as default port):

doc/knowledgebase/IWKB000005.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Now open a new PowerShell session again and check of the new directory was added
8383
Once the directory is there, restart the `icingapowershell` service by running
8484

8585
```powershell
86-
Restart-IcingaWindowsService;
86+
Restart-IcingaForWindows;
8787
```
8888

8989
Now the error should be resolved the the service should be running.
@@ -119,7 +119,7 @@ Now open a new PowerShell session again and check of the new directory was added
119119
Once the directory is there, restart the `icingapowershell` service by running
120120

121121
```powershell
122-
Restart-IcingaWindowsService;
122+
Restart-IcingaForWindows;
123123
```
124124

125125
Now the error should be resolved the the service should be running.

doc/knowledgebase/IWKB000014.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Import-Module -Name 'icinga-powershell-framework' -Global -Force;
3636
3737
icinga { Write-Host 'Icinga for Windows successfully repaired' };
3838
39-
Restart-IcingaWindowsService;
39+
Restart-IcingaForWindows;
4040
```
4141

4242
Once executed, Icinga for Windows should rebuild the cache and work again as intended. Please keep the `icinga` call within the example, as this will ensure that possible pending migrations of Icinga for Windows will be applied.

0 commit comments

Comments
 (0)