gitlab requires specific workflow to setup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gitlab (Juju Charms Collection) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm using gitlab inside juju-quickstart's GUI, and it seems much harder to use than other charms. It seems that, for this charm, the only working workflow is the documented one:
add service to canvas
set the password
add the relation with mysql
only then start it
(Note, though, that the README does not actually document that in full — it says "edit config.yaml", which means little in juju's web interface).
Otherwise, it seems you always end up in stuck states. However, other charms are more flexible. Juju imposes a much more flexible state machine for the state of a charm, and essentially requires that you can do your configuration steps in arbitrary order, as long as in the end you make all of them.
Part of the problem is the already assigned https:/
Setting the password later fails — the service gets stuck if you don't set the password before starting it (https:/
Changing the configuration also fails (https:/
Adding the relation later also failed for me, like https:/
