Cherry-pick #7887 to 6.4: Allow custom port in cloud.id #7904
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #7887 to 6.4 branch. Original message:
Make it possible for the the cloud.id to contain a custom port. If the port is not specified, 443 is used, like before.
The custom port can be specified in multiple ways. The cloudid is formed like this:
<host>:<es-id>:<kb-id>
. The port can be specified either in es-id or kb-id, or in the host section. If specified in both, the more specific one wins (i.e. es-id over host).Examples:
Results in:
Or:
Results in:
This is proposed fix for #7794.