juju-deployer local-mods command is counter intuitive and thus confusing

[Jeff Lane]

looking at juju-deployer -h it says this:

-L --local-mods Disallow deployment of locally-modified charms

That is exactly the opposite of what one would expect from specifying that switch.

A good analogy would be like using -v to suppress verbosity rather than enable it.

Also looking at the help, there doesn't seem to be any obvious way to tell juju-deployer to use a local repo instead of one from the charm store.

[Kapil Thangavelu (hazmat)]

do you have a suggestion for an alternative re -L? Else i'm inclined to just leave as is afaics the only change here would be
-L --disable-local-mods. Deployer already has 101 options..

re your support question..

export JUJU_REPOSITORY=my_repository

drop your charms into my_repository/precise and then a simple deployer file would be.

mycloud-ssl:
  series: precise
  services:
    mysql:
      charm: mysql
      options:
        ssl: only
    keystone:
      charm: keystone
    cinder:
      charm: cinder
      options:
        block-device: None
    glance:
      charm: glance
    nova-cc:
      charm: nova-cloud-controller

  relations:
    - [mysql, [cinder, glance, nova-cc, keystone]]

[Kapil Thangavelu (hazmat)]

The flag doc string on this was cleared up to reflect usage.