Remove support for setting server.host to '0' (breaking)

[watson]

Support for this was originally a side-effect of our old version of hapi (pre v20). hapi v20 does no longer support this, so a workaround was added to not break expectations. This PR removes that workaround for v8.0.0 as it's considered a breaking change.

Besides, in the new version of joi, 0 is no longer considered a valid hostname, so when we upgrade, this extra validate function can be removed.

Todo

• Ensure snapshots run via Docker doesn't use 0 as their server.host (Use 0.0.0.0 instead of 0 as server.host elastic-package#211)
• Update docs to not use 0
• Any other places where we have hardcoded 0??

Release note

Removes support for configuring Kibana with 0 as the server.host.

[watson]

@graphaelli You mentioned that we list 0 as a valid config option in the docs somewhere. Do you mind pointing me in the right direction?

[spalger]

Docker config change LGTM, but want to make sure @jbudz sees this and doesn't have any issue with it.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3fec5d3

Metrics [docs]

Distributable file count

id	before	after	diff
default	47262	48025	+763

History

• 💚 Build #96676 succeeded 3934f8e
• 💚 Build #96566 succeeded ee6752c9d4675ea7ac099924e86b97a0e521b4e9

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 87114 or prevent reminders by adding the backport:skip label.