canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #03587
[Merge] ~andersson123/autopkgtest-cloud:upgrade-charm-to-docs into autopkgtest-cloud:master
Tim Andersson has proposed merging ~andersson123/autopkgtest-cloud:upgrade-charm-to-docs into autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/463293
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:upgrade-charm-to-docs into autopkgtest-cloud:master.
diff --git a/docs/deploying.rst b/docs/deploying.rst
index 13fd5bb..d749a57 100644
--- a/docs/deploying.rst
+++ b/docs/deploying.rst
@@ -131,6 +131,15 @@ Making configuration changes
Edit the ``service-bundle`` file as above, and run ``mojo run`` again.
+If, however, you're doing a charm update that only involves code changes,
+without any required changes to ``juju config`` options, you can run
+the following script:
+
+``autopkgtest-cloud/mojo/upgrade-charm``
+
+Which will update the code for all the charms with the latest revision in
+charmhub, without running all the various ``mojo run`` stages.
+
autopkgtest-cloud Storage
----------------------------
@@ -190,10 +199,14 @@ Where $charm is either equal to "web" or "cloud-worker".
Then run ``mojo run`` on the system where you want to deploy the update - this
will pull the updated charm from the charm store.
-Please note, if you have made changes to the charm that add new package dependencies,
-a mojo run will not update this on the relevant units. For this to take place, you must
-either ``remove-unit`` and ``add-unit`` the relevant unit, or install the new dependencies
-manually on the unit.
+If, however, you're doing a charm update that only involves code changes,
+without any required changes to ``juju config`` options, you can run
+the following script:
+
+``autopkgtest-cloud/mojo/upgrade-charm``
+
+Which will update the code for all the charms with the latest revision in
+charmhub, without running all the various ``mojo run`` stages.
Tagging the charm revisions
---------------
Follow ups