Description of problem: BZ 1144788 addressed the issue of exposing the TLS port mapping as env vars. But it only sets those vars in the control script, not the install script.
https://issues.jboss.org/browse/ENTESB-1952
I think this is fundamentally impossible for us given our current goals... the flow of gear creation is: 1) run install/setup steps 2) connect the gear to the external router it's at step 2 that the ports are assigned/identified for TLS (among other things), so we can't set the env variables until then without a major reworking.
The TLS ports for a node are static. How hard can this be?
Hiram Chirino <hiram> updated the status of jira ENTESB-1952 to Resolved
Marek Schmidt <maschmid> updated the status of jira ENTESB-1952 to Closed