~verterok/mojo/ignore-app-wait-support

Committer: mergebot at canonical
Author(s): "Barry Price"
Date: 2023-08-15 09:34:36 UTC
mfrom: (602.1.1 mojo)
Revision ID: mergebot@juju-139df4-prod-is-toolbox-0.canonical.com-20230815093436-dv2wfuiibg96cct2

Explicitly document that bundle phases will apply charm upgrades, refer to 'charmhub' over 'charm store'

Reviewed-on: https://code.launchpad.net/~barryprice/mojo/trunk/+merge/449181
Reviewed-by: Tom Haddon <tom.haddon@canonical.com>

files modified:
docs/mojo/readme.md

Show diffs side-by-side

added added

removed removed

docs/mojo/readme.md

677

service. This is analogous to the deployer phase's apply-config-changes being set to

678

True.

679

680

In the same way, bundle phases will also apply any available upgrades to running charms

681

if the source defined in the bundle is newer than the running version.

682

680

683

Also important to be aware of is how bundles specify charm locations. Where juju-deployer

681

684

was able to deduce the location of charms from the mojo environment variables, bundles

682

685

require that you explicitly specify a path to a local charm if that's what you intend to

685

688

charm: {{ charm_dir }}/haproxy

686

689

687

690

This specifies the full path to a multi-series charm fetched locally by codetree. Of course

688

you can also use charm store charms by simply prepending your charm name with cs: in the

689

bundle and this is implicit if no path is specified, so bundles default to deploying charm

690

store charms.

691

you can also use charmhub charms by simply prepending your charm name with ch: in the

692

bundle and this is implicit if no path is specified, so bundles default to deploying charmhub

693

charms.

691

694

692

695

693

696

Older »