Ubuntu – How to retrieve and list local charms in juju-gui charm browser

I believe I see your problem. So, you pulled this charm from github which is fine. However, tests are usually written and run from within the tests directory. So, amulet applies a little bit of magic to deploy using the charm on disk so you don't have to explicitly put charm= in the d.add line. However, since you're running from interactive shell it makes sense for you to do this. The problem is, it's not a Bazaar branch which is what Juju Deployer is expecting.

Typically, what happens, when you just do d.add('cf-nats') in a charm test, the charm tree gets copied to a temporary location, and a bzr repo is created (if one doesn't exist already). Then that new temp location is fed to deployer. However, since you've given it a firm file path that part isn't happening (by design) and it assumes you have a charm that has a bzr repo and it's just going to use that.

The way around this is to either run export JUJU_TEST_CHARM="cf-nats" (and environment variable the juju test plugin sets) prior to launching your Python3 shell from the $CHARM_DIR (/home/ubuntu/cf-charms/charms/trusty/cf-nats) or after creating d = amulet.Deployment() set d.charm_name = 'cf-nats'. Then just do d.add('cf-nats'), amulet will see that the basename of getcwd is the same as the charm name and transparently perform it's little bit of magic.

That should do it. Ideally, adding support for git based charms to juju deployer will resolve all of this, but try that and let me know if it doesn't work for you.

To add your charms to the left column, the Charm Browser, you need to create the appropriate repository in Launchpad (step-by-step guide).

To deploy a local charm via the gui you need to zip up the contents of your charm in the correct directory structure for a charm and drag and drop that zip onto the canvas. It will then guide you through the process of deploying that charm to your environment.