juju-deployer

does not honor charm path when set in configuration

Bug #1237582 reported by David Lawson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-deployer
Incomplete
Medium
Unassigned

Bug Description

juju-deployer must be run from the directory immediately above series/charm-name/ otherwise it fails to find the charms referenced in the deployment configuration, even if those charms are expressed as a full path. juju-deployer should honor the paths set in the configuration and not require that it be run from any particular directory.

This is with 0.2.3+bzr115-0~26~precise1ubuntu1, which appears to be an IS packaged version.

David Lawson (deej)
tags: added: canonical-webops
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

as an alternative deployer honors JUJU_REPOSITORY, does that work for you?

Changed in juju-deployer:
status: New → Incomplete
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

Also latest version of deployer is available off pypi (pip install juju-deployer) and is rev 0.3.2.

Changed in juju-deployer:
importance: Undecided → Medium
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

The alternative requires us to bypass using the juju cli and directly zip the charm dir and upload to juju via the api. That's doable but its something i'd only want to handle post dropping pyjuju support.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.