cf-charmers team mailing list archive

[prismakov@xxxxxxxxx]

Thank you, Kapil, I altered bundle.yaml to use ‘expose’ instead of ‘exposed’ and now it works well.
I’ve added tag ‘v001’ to all charms but I can’t find how to specify it in address.
I guess I need change bundle file to use smth like:
'branch: lp:~cf-charmers/charms/trusty/cf-nats/trunk@v001’ ?

How to do it correctly?

-Alexander Prismakov

 On Apr 7, 2014, at 15:43, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx> wrote:

> re router exposing.. adding expose: true  to the bundle should resolve.
> 
> 
> On Mon, Apr 7, 2014 at 8:43 AM, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx> wrote:
> The bundle supports @ revision syntax for version pinning on charm branch urls, so you can just tag the bundle repo.
> 
> 
> On Mon, Apr 7, 2014 at 12:19 AM, <prismakov@xxxxxxxxx> wrote:
> Congrats guys!
> 
> After resolving several minor issues I've managed to deploy CF bundle with Juju bundler and publish an application to it. Application runs and answers to requests.
> So we are ready for CATs (Cloud foundry Acceptance Tests). Only one remaining issue is that bundler not expose the router. Destroying also works well.
> I think we need tag current version of charms.
> 
> 
> -Alexander Prismakov
> 
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
> 
> 
>