Issue 191940043: Support deploying bundles from custom users.
DescriptionSupport deploying bundles from custom users.
Also add the charmstore-url charm option so
that the new GUI can properly connect to the
charm store.
Update the deployer version (we use a fork for now)
and the GUI server so that both the user and the
password are provided when calling the deployer
blocking functions.
If you are curious, the deployer merge proposal is here:
https://code.launchpad.net/~frankban/juju-deployer/guiserver-auth/+merge/244984
Tests: `make unittest`.
QA:
- bootstrap an environment with juju 1.21;
- deploy this charm by using `make deploy`;
- wait for the charm to be ready;
- switch to the most recent GUI:
`juju set juju-gui juju-gui-source=develop`;
- while waiting, create a new juju user:
`juju user add new-user --generate`;
- copy to clipboard the password included in the
resulting new-user.jenv file;
- wait for the trunk release to be ready;
- visit the GUI and log in using "new-user" and
the copied password;
- ensure the charm browser is correctly displayed, meaning
the charm properly connects to the charm store;
- search for a bundle in the browser and deploy it: you should
get this error: "An error occurred while deploying the bundle:
Invalid relation in config, service 1 not found, rel 1 <-> 0
Invalid relation in config, service 0 not found, rel 1 <-> 0"
or similar... This is another issue. Dragging and dropping an old
bundle from your desktop should instead work;
- destroy the environment.
Done, thank you!
https://code.launchpad.net/~frankban/charms/trusty/juju-gui/new-deployer-auth/+merge/245011
(do not edit description out of merge proposal)
Patch Set 1 #
Total comments: 4
Patch Set 2 : Support deploying bundles from custom users. #
MessagesTotal messages: 5
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
