lp://staging/~hatch/charms/trusty/juju-gui/hide-login-button

Created by Jeff Pihach and last modified
Get this branch:
bzr branch lp://staging/~hatch/charms/trusty/juju-gui/hide-login-button
Only Jeff Pihach can upload to this branch. If you are Jeff Pihach please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Jeff Pihach
Status:
Development

Recent revisions

225. By Jeff Pihach

Converted showGetJujuButton to hideLoginButton to match UI changes in the GUI

224. By Francesco Banconi

Support 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!

R=
CC=
https://codereview.appspot.com/191940043

223. By Francesco Banconi

Add the Juju version to the GUI config file.

The version can be specified using a charm option.
If not specified, the Juju version is retrieved
dynamically by calling jujud --version.

Initial implementation by Huw.

Tests: `make unittest`.

QA:
- bootstrap an environment;
- run `make deploy`;
- wait for the unit to be ready;
- run `juju ssh juju-gui/0 cat /var/lib/juju-gui/juju-gui/build-prod/juju-ui/assets/config.js`
  and check the Juju version is included in the config file;
- run `juju set juju-gui juju-core-version=42.47`;
- check the version is changed to the one specified;
- run `juju unset juju-gui juju-core-version`;
- check the correct version is back in the config file;
- destroy the environment.

Done, thank you!

R=rharding
CC=
https://codereview.appspot.com/188890043

222. By Jeff Pihach

Merged back the new charm release.

221. By Jeff Pihach

Updated to the newest juju-gui release.

220. By Francesco Banconi

Merged back the new charm release.

219. By Richard Harding

Update README to reflect recent changes.

218. By Francesco Banconi

Merged back the new charm release.

217. By Francesco Banconi

Updated to the newest juju-gui release.

216. By Francesco Banconi

Merged changes from the released charm.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp://staging/charms/juju-gui
This branch contains Public information 
Everyone can see this information.

Subscribers