Invalid G/W port in API path about dispatch HOT 5 CLOSED

cc @kars7e @zimengyang

from dispatch.

@neosab Here is the reason, In #709
the api gateway port is read from dispatch config file. but in the ova, the file don't contain api-https-port and api-http-port, so it show as default api gateway port 8444 and 8081.
So I think we should modify the config file

from dispatch.

@pzmrzy Why is the server reading from config file? It must be reading from the --gateway-tls-port 443 flag right

from dispatch.

Yes, the server read the flag, but client read the config file
When do dispatch get api, the server return only the relative url.
The port is been add in the client side

from dispatch.

I missed that the URL is constructed by the client. Yup, in that case, we should fix the config file in the OVA.

from dispatch.