Exporting from real environment exports juju-gui as well

[Jeff Pihach]

On a real environment when you export your environment the export includes the juju-gui charm but this will cause the bundle to be un-deployable using the GUI on any other real environment because there will already be a service called juju-gui.

[Gary Poster (gary)]

I'd rather have a GUI import have an option to ignore the GUI. If you are exporting the environment, the GUI is in the environment.

[Richard Harding (rharding)]

See https://bugs.launchpad.net/charm-tools/+bug/1290444 for more information as well. Thinking on this more now.

WIth quickstart auto creating gui instances in environments and the ability to deploy multiple bundles to an environment it seems that this gui issue is very annoying.

I'm not tempated to just auto remove the GUI on export and error on bundle proof. If it's in the store and meant to be reused there are too many variables to deal with. Just leaving out the gui makes things at least a bit more predictable.

[Richard Harding (rharding)]

This bug is really meant on export. Quickstart shouldn't have to worry about it. If the user has the gui in there and uses export then they should pull it out. If we get where there's some need to specify config on the gui instance in the real env, we can investigate a way to do this properly.