Bundle deployment in sandbox is confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-gui |
Triaged
|
Low
|
Unassigned |
Bug Description
It is not clear whether or not deploying a bundle in the sandbox will deploy it to your current JUJU_ENV (as it says on the confirmation button) or within the sandbox. Additionally, the export link could be more clear that it applies to the canvas, not the embedded bundle topology:
<ppetraki> has anyone tried to download a bundle lately from the charm store? I've tried to export several different ones and all I'm getting is
<ppetraki> envExport:
<ppetraki> services: {}
<ppetraki> relations: []
<ppetraki> series: precise
<lazyPower> that one ^
<rick_h_> lazyPower: no, what's up?
<rick_h_> ppetraki: oh looking
<rick_h_> ppetraki: hmm, how are you downloading? Is this when you build an environment on jujucharms.com and hit export?
* ppetraki digs up example
<rick_h_> ppetraki: I just did a qiuck test and it worked. I wonder if you're trying to do something differently or with something that's not working?
<rick_h_> ppetraki: screenshot of your environment would be useful to replicate on jujucharms.com to test out
<ppetraki> ack
<rick_h_> ppetraki: thanks, we'll help look into it for sure. Thanks for the report of the issue.
* rick_h_ goes afk for a few to migrate home from coffee shop
<ppetraki> rick_h_, http://
<ppetraki> rick_h_, I just visit the bundle, click the '^', and open the file it downloaded
<Makyo> ppetraki, deploy the bundle to the GUI first. The ^ button exports the canvas, not the charm or bundle you are viewing.
<Makyo> Will take a note, though, that's worth clarifying.
<Makyo> ppetraki, if you wish to grab a bundle's code from the store without deploying, you can go to the code tab, eg https:/
<ppetraki> Makyo, it says it'll be deployed to my local provider immediately, does that mean my current juju-env?
<Makyo> ppetraki, if you are viewing it at jujucharms.com, the provider is the demonstration provider, which is just a sandbox within the browser.
<ppetraki> Makyo, yeah, as a regular user I have no idea what the difference is
<ppetraki> and assumed the worse
* ppetraki well, im not exactly a regular user
<Makyo> ppetraki, that's totally fair. We'll see if there's a way to make that more clear.
<ppetraki> Makyo, thanks
<Makyo> jujugui call in 10
<lazyPower> ah thats something I didnt think about, that charms are transient until you actually "deploy" them on the gui
This is very interesting. It's not something I've thoght about before. We have future plans for the bundle visualizations to take more more screen real estate and have a more clear distinction between the canvas and other views. I think it would make sense to show/hide the import/export controls in reaction to what view you're using. We will bring this up when designing those interactions.