The areas users interface with juju are:
- jujucharms.com urls - charm push/pull commands - juju cli deploy commands - juju gui URLs (similar to jujucharms.com)
Currently the patch to a charm or bundle are not the same across these areas. This can lead to confusion from a user experience perspective.
Ideally if a user knows the path that works in the same format where ever they have to type it in. So the following are all the same path syntax:
$ juju deploy ~<id>/bundle/<bundle-name>-<revision> $ charm push . ~<id>/bundle/bundle-name https://jujucharms.com/u/<id>/<bundle-name>/bundle/<revision>
The areas users interface with juju are:
- jujucharms.com urls
- charm push/pull commands
- juju cli deploy commands
- juju gui URLs (similar to jujucharms.com)
Currently the patch to a charm or bundle are not the same across these areas. This can lead to confusion from a user experience perspective.
Ideally if a user knows the path that works in the same format where ever they have to type it in. So the following are all the same path syntax:
$ juju deploy ~<id>/bundle/ <bundle- name>-< revision> bundle- name /jujucharms. com/u/<id>/<bundle- name>/bundle/ <revision>
$ charm push . ~<id>/bundle/
https:/