-
Notifications
You must be signed in to change notification settings - Fork 323
Closed
Description
When binding a app to a tcp route, and then retrieving the application details for the app, the uris for the app do not include port information.
Sample code to reproduce is here: https://github.com/kdvolder/cf-java-client-sample-v2/tree/ec98ba2fb29ceb072b6cca4478f42c17281b80e2
Run the main class here:
It pushes an app with the following manifest:
applications:
- name: test-static-aaasd
buildpack: staticfile_buildpack
path: testapp.zip
Then it uses operations api to bind an additional tcp route to the app. (I couldn't directly bind tcp route from the manifest because of the other bug Paul just fixed).
At the end of the output of this run you'll find the following:
app deployed at: [tcp.local2.pcfdev.io, test-static-aaasd.local2.pcfdev.io]
Notice that tcp.local2.pcfdev.io
doesn't have the port information, only the domain.
This is not the behavior as I'd expect. Compare to cf cli for example:
$ cf apps
Getting apps in org pcfdev-org / space pcfdev-space as admin...
OK
name requested state instances memory disk urls
test-static-aaasd started 1/1 256M 512M tcp.local2.pcfdev.io:61001, test-static-aaasd.local2.pcfdev.io
$ cf app test-static-aaasd
Showing health and status for app test-static-aaasd in org pcfdev-org / space pcfdev-space as admin...
OK
requested state: started
instances: 1/1
usage: 256M x 1 instances
urls: tcp.local2.pcfdev.io:61001, test-static-aaasd.local2.pcfdev.io
last uploaded: Fri Jun 16 16:12:57 UTC 2017
stack: cflinuxfs2
buildpack: staticfile_buildpack
state since cpu memory disk details
#0 running 2017-06-16 09:13:10 AM 0.0% 3.2M of 256M 6.1M of 512M