cf-charmers team mailing list archive
-
cf-charmers team
-
Mailing list archive
-
Message #00411
Re: Resolve port conflicts in cf-go-router (issue 103270043 by johnsca@xxxxxxxxx)
On 2014/06/11 22:23:56, benjamin.saller wrote:
> hooks/config.py:39: 'ports': [80],
> if this is a config option (and it can be because we expose this one)
then this
> can't be hard-coded here.
> The harder issue is that we then need to track the previous value if
we are to
> close the old port.
Thanks, good catches. I added the logic to close the old port when
switching to charm-helpers because it should always happen, and I feel
like it should be transparent to the charm author.
https://codereview.appspot.com/103270043/
--
https://code.launchpad.net/~johnsca/charms/trusty/cf-go-router/port-conflicts/+merge/222671
Your team Cloud Foundry Charmers is requested to review the proposed merge of lp:~johnsca/charms/trusty/cf-go-router/port-conflicts into lp:~cf-charmers/charms/trusty/cf-go-router/trunk.
References