cf-charmers team mailing list archive

[Alexander Lomov <lomov.as@xxxxxxxxx>]

Hello again.
Alexander suggested some work arounds for this questions I've asked:
1. getting normal (not lightweight) checkouts is not what we really need,
we need option that allows us to use local repository (with normal
checkouts) as sources for deployer. I think it can be possible to use local
repository as a branch in the bundle file (I mean this option
http://bazaar.launchpad.net/~cf-charmers/charms/bundles/cloudfoundry/bundle/view/head:/bundle.yaml#L10).
also using different bundle files for different branches supposed to be a
good practice.
2. `expose` option already exists (I think I could use wrong version
http://bazaar.launchpad.net/~cf-charmers/charms/bundles/cloudfoundry/bundle/revision/6
)

Thank you,
Alex.


On 8 April 2014 20:54, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hey, Kapil.
>
> Here are some questions/suggestions regarding juju-deployer:
>
> - It would be really useful if deployer had ability to use local
> repositories with normal (not lightweight) checkouts, it will allow to
> commit change and to deploy using one branch.
> - Is there any bundle config option to expose service after deploy?
> Currently we don't have this feature in our bundle.yaml.
>
> Best wishes,
> Alex.
>