-
Notifications
You must be signed in to change notification settings - Fork 31
Description
Problem
When running the Install-Icinga
Command, incorrect values for (or mandatory but missing) parameters drop you to an interactive menu.
For manual installations this is perfect since you can simply correct your errors in the wizard.
If however you are trying an automatic approach, you might lock the session (PowerShell) indefinetely.
Using Ansible I basically create an InstallCommand
from a template. If the user or Ansible does something wrong, the Ansible task never finishes and just idles for ever (because we got dropped to the interactive prompt without any way to leave).
The only measure against this is a timeout (which might kill "good" processes that just happen to take longer than timeout
).
Desired change
I would like to have a parameter like -NoInteractive
that would cause the command to simply exit with failure instead of dropping into the interactive menu (in case of errors of course).
If -NoInteractive
is not given, the old behaviour should be kept. This way, both approaches have a reliable workflow.
If automation fails, it's almost certainly user error. Thus failing early (before timeout) saves time in the long run.