Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Add the juju 2.0 ability to use resources in Amulet #142
Comments
|
To test fetching from the controller, it seems like you would need the ability to push them to the controller first. |
simonklb
commented
Oct 10, 2016
|
I'm also trying to create a test for a charm that uses resources. Curious, did you work around this somehow or have you put it on hold until support for resources is implemented? |
|
This is a pretty significant issue because it prevents testing any charms that have resources. Because Amulet is intended to test a charm during dev, it almost always deploys the charm in question from a local copy which causes the charm store resources to not be used. We need a way to tell Amulet, "you're using a local copy of this charm store URL, so use those remote resources." |
mbruzek commentedJul 11, 2016
I am trying to develop tests for a charm that only uses the juju 2.0 resources feature. The charm fails to find the resource and does not install the package. The amulet code should have some way to add and remove resources to test these kind of charms.
Relevant information:
The charm command
resource-getwill fetch a resource from the Juju controller or the Juju Charm storePlease note there are two types of commands, the
jujuresource commands and thecharmresource commands. Thejujuresource commands only attach, or list resources for the current controller. Thecharmcommands attach and retrieve from the Charm Store.I suspect that an MVP for Amulet will not include attaching resources, but we will need to test
resource-getfrom both the controller and Charm Store.