auto-deploy when installing an app is blocked by warnings in the preflight checks

[sgalsaleh]

there are two proposals for handling this:

1- just ignore any warning level checks and only block on errors
2- allow a flag to bypass, for example --ignore-preflight-warnings

[markpundsack]

IMHO, warnings should not block unattended installations. I was surprised when we blocked web installations for warnings, but understand the decision since it's just a confirmation away. But with unattended, the same is not true. I'm against adding a flag to bypass since then we teach users to just bypass warnings anyway, and at some point there will be a real warning they shouldn't have ignored. If we had a way to ignore specific warnings, that would be different, but that's a lot more complicated of a solution that isn't worth it.

@marccampbell pointed out that our docs to explicitly mention passing:

Once this has completed, visiting http://localhost:8800 will show the configured application dashboard, assuming all required config items were set and any included preflight checks passed.

But looking at the docs, in colloquial English, warnings are passed. In GitLab, for example, CI jobs show as “passed with warnings”. If I were running a CLI, the exit code for a command would be “success” even if there were warnings.

[austinchambers]

We should consider allowing the same capability on errors as well (e.g., --ignore-preflight-errors).