Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the juju 2.0 ability to use resources in Amulet #142

Open
mbruzek opened this issue Jul 11, 2016 · 4 comments
Open

Add the juju 2.0 ability to use resources in Amulet #142

mbruzek opened this issue Jul 11, 2016 · 4 comments

Comments

@mbruzek
Copy link
Contributor

mbruzek commented Jul 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-get will fetch a resource from the Juju controller or the Juju Charm store

Please note there are two types of commands, the juju resource commands and the charm resource commands. The juju resource commands only attach, or list resources for the current controller. The charm commands 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-get from both the controller and Charm Store.

@johnsca
Copy link
Contributor

johnsca commented Jul 11, 2016

To test fetching from the controller, it seems like you would need the ability to push them to the controller first.

@simonklb
Copy link

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?

@johnsca
Copy link
Contributor

johnsca commented Mar 2, 2017

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."

@rmescandon
Copy link

What's the status of this?. Is there any way to workaround it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants