Optimizes IMC and centralizes data

Author: LordHepipud

doc/100-General/01-Upgrading.md

@@ -16,7 +16,7 @@ Otherwise the service will not start and crash! You can either download the serv
 Update-Icinga -Name 'service';
 ```
 
-After upgrading to Icinga for Windows v1.8.0, you will require to open a new Icinga shell by calling `icinga` or by using `Use-Icinga` once, to run the new migration process.
+After upgrading to Icinga for Windows v1.8.0, you will require to open a new Icinga shell by calling `icinga -Shell` or simply `icinga` to open the IMC for running the migration tasks.
 
 **NOTE:** In some cases the changes for the EventLog will only apply, **after** the system has been rebooted. Afterwards every Icinga for Windows EventLog entry is written in a newly created `Icinga for Windows` log.
 

doc/100-General/10-Changelog.md

@@ -50,6 +50,7 @@ Released closed milestones can be found on [GitHub](https://github.com/Icinga/ic
 * [#445](https://github.com/Icinga/icinga-powershell-framework/pull/445) Adds command `Repair-IcingaService` to repair Icinga Agent service in case it was broken during upgrades, mostly caused by `The specified service has been marked for deletion`
 * [#448](https://github.com/Icinga/icinga-powershell-framework/pull/448) Adds support to sort arrays without ScriptBlocks
 * [#450](https://github.com/Icinga/icinga-powershell-framework/pull/450) Improves show command `Show-IcingaRegisteredServiceChecks`, adds new command `Show-IcingaRegisteredBackgroundDaemons` and extends `Show-Icinga` by both commands and adds debug and api forwarder features to environment list
+* [#453](https://github.com/Icinga/icinga-powershell-framework/pull/453) Reworks Icinga Management Console menu structure and naming and changes the default behavior of executing `icinga` to now open the IMC by default and `icinga -Shell` to open a shell as done previously
 * [#455](https://github.com/Icinga/icinga-powershell-framework/pull/455) Adds support for remote execution plugin [check_by_icingaforwindows](https://github.com/LordHepipud/check_by_icingaforwindows)
 
 ## 1.7.1 (2021-11-11)

doc/110-Installation/02-Icinga-Management-Console.md

@@ -5,7 +5,7 @@ As we now have deployed our Icinga PowerShell Framework on our Windows machine,
 **Note:** You can always open the IMC by running the following command:
 
 ```powershell
-icinga -Manage;
+icinga;
 ```
 
 ## Navigating the IMC

doc/110-Installation/03-Installation-with-IMC.md

@@ -5,7 +5,7 @@ We can now use the Icinga Management Console to configure our local Windows syst
 If we are not already inside the IMC, we can open it with
 
 ```powershell
-icinga -Manage;
+icinga;
 ```
 
 ## Installation menu

doc/160-Features/04-Manage-Icinga-Agent-Features.md

@@ -2,7 +2,7 @@
 
 The Icinga PowerShell Framework is shipping wish a bunch of Cmdlets to manage the Icinga Agent in a very easy way. This includes the managing for features enabled or disabled for the Icinga Agent.
 
-**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `Use-Icinga`. Starting with version `1.2.0` of the Framework you can also simply type `icinga` into the command line.
+**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `icinga -Shell`
 
 ## List Icinga Agent Features
 

doc/160-Features/05-Read-Icinga-Agent-Logs.md

@@ -2,7 +2,7 @@
 
 The Icinga PowerShell Framework is shipping wish a bunch of Cmdlets to manage the Icinga Agent in a very easy way. This includes reading the Icinga Agent log/debug log file.
 
-**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `Use-Icinga`. Starting with version `1.2.0` of the Framework you can also simply type `icinga` into the command line.
+**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `icinga -Shell`
 
 ## Read the default Icinga Agent log file
 

doc/160-Features/06-Test-Icinga-Installation.md

@@ -2,11 +2,11 @@
 
 The Icinga PowerShell Framework is shipping wish a bunch of Cmdlets to manage the Icinga Agent in a very easy way. This includes a test for the entire configuration and state of the Icinga Agent on the machine.
 
-**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `Use-Icinga`. Starting with version `1.2.0` of the Framework you can also simply type `icinga` into the command line.
+**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `icinga -Shell`
 
 ## Testing for errors
 
-A very important part of an Agent is to ensure that it is running properly and no configuration error is present. In addition it is important that required directories are accessable by the service user the Icinga Agent is running with. For this you can use the Cmdlet `Test-IcingaAgent`:
+A very important part of an Agent is to ensure that it is running properly and no configuration error is present. In addition it is important that required directories are accessible by the service user the Icinga Agent is running with. For this you can use the Cmdlet `Test-IcingaAgent`:
 
 ```powershell
 Test-IcingaAgent;
@@ -51,7 +51,7 @@ In addition for testing, the Icinga PowerShell Framework will suggest methods to
 [Passed]: Icinga Agent debug log is disabled
 ```
 
-As you can see, the mandatory directory `C:\ProgramData\icinga2\var` is not accessable by our `NT AUTHORITY\NetworkService` user. To resolve this, the Framework provides the Cmdlet `Set-IcingaAcl`. It will automatically set the correct permissions for a specific directory for the service user the Icinga Agent is running with:
+As you can see, the mandatory directory `C:\ProgramData\icinga2\var` is not accessible by our `NT AUTHORITY\NetworkService` user. To resolve this, the Framework provides the Cmdlet `Set-IcingaAcl`. It will automatically set the correct permissions for a specific directory for the service user the Icinga Agent is running with:
 
 ```powershell
 Set-IcingaAcl -Directory 'C:\ProgramData\icinga2\var';
@@ -97,7 +97,7 @@ As our configuration is for some reason broken we have to resolve this. The Icin
 Test-IcingaAgentConfig -WriteStackTrace | Out-Null;
 ```
 
-By using the argument `-WriteStackTrace` we will print the actual error ouptut from the Icinga Agent binary to our console for troubleshooting:
+By using the argument `-WriteStackTrace` we will print the actual error output from the Icinga Agent binary to our console for troubleshooting:
 
 ```text
 [2020-08-12 16:54:26 +0200] information/cli: Icinga application loader (version: v2.12.0)

doc/160-Features/20-Change-Icinga-Service-User.md

@@ -2,7 +2,7 @@
 
 The Icinga PowerShell Framework is shipping wish a bunch of Cmdlets to manage the Icinga Agent in a very easy way. This includes changing the current assigned Service User of the Icinga Agent to another one.
 
-**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `Use-Icinga`. Starting with version `1.2.0` of the Framework you can also simply type `icinga` into the command line.
+**Note:** Before using any of the commands below you will have to initialize the Icinga PowerShell Framework inside a new PowerShell instance with `icinga -Shell`
 
 ## Getting started
 

doc/900-Developer-Guide/52-Testing-of-Commands.md

@@ -1,14 +1,6 @@
 # Developer Guide: Testing of Commands
 
-Actively developing new code for the Framework will result in core files to be changed or new functionality added. To load the Framework we use in general `Use-Icinga`, which does how ever not cover changes we made afterwards. To keep track of the changes for new features or while testing something, we always have to open a new PowerShell instance.
-
-To make things more usable, we can of course run a PowerShell command directly from our shell:
-
-```powershell
-powershell -C { Use-Icinga; <# your code #> }
-```
-
-While this is straight forward and easy to use, the idea is to make this way simpler.
+Actively developing new code for the Framework will result in core files to be changed or new functionality added. To load the Framework we use in general `icinga -Shell`, which does how ever not cover changes we made afterwards. To keep track of the changes for new features or while testing something, we always have to open a new PowerShell instance.
 
 ## Invoke-IcingaCommand or simply icinga
 
@@ -58,7 +50,7 @@ icinga> Exit-IcingaThrowException -Force -CustomMessage 'Force Exit of our Shell
 Unhandled exception occured:
 ```
 
-Instead of our own shell closing, we still have our previous one open and can start another shell by using `icinga` with the entire Framework loaded.
+Instead of our own shell closing, we still have our previous one open and can start another shell by using `icinga -Shell` with the entire Framework loaded.
 
 This also works for code we directly invoke to the `icinga` alias:
 

doc/950-Deprecated/04-Icinga-Agent-Wizard.md

@@ -10,7 +10,7 @@ To start the Icinga Agent installation wizard you will have to open a PowerShell
 Use-Icinga
 ```
 
-*Note:* Starting with Icinga PowerShell Framework `1.2.0` you can simply type `icinga` to open an Icinga PowerShell Framework shell,
+*Note:* Starting with Icinga PowerShell Framework `1.2.0` you can simply type `icinga -Shell` to open an Icinga PowerShell Framework shell,
 
 Once the command is executed, the Framework and all required components are loaded. To get started, we can now run