Merge ~andersson123/autopkgtest-cloud:upgrade-charm-to-docs into autopkgtest-cloud:master

[Tim Andersson]

[Skia (hyask)]

I'm not sure I'm the best person to approve this. Moreover, I have uncertainties around the upgrade of charms, like what would happen to the rabbitmq charm that we fixed on a particular version in the service-bundle?

[Tim Andersson (andersson123)]

It stays pinned to the version in the juju config I believe, I've been using this script for a long time with no issues as an alternative to mojo run when all that's needed is a code update

[Tim Andersson (andersson123)]

ping on this. The upgrade-charm script adheres to version pinning and channel pinning as in the service-bundle. Please re-review

[Skia (hyask)]

review: Needs Fixing

[Tim Andersson (andersson123)]

amended and ready for re-review

Unmerged commits

98af218... by Tim Andersson on 2024-03-28

docs: remove mention of new dependencies requiring a unit replacement

	pre_commit:0 (build)
	unit_tests:0 (build)
	build_charms:0 (build)

1 → 3 of 3 results

First • Previous • Next • Last

aa1780a... by Tim Andersson on 2024-03-28

docs: mention upgrade_charm script in Deploying section

diff --git a/docs/deploying.rst b/docs/deploying.rst
index 13fd5bb..8a6dd64 100644
--- a/docs/deploying.rst
+++ b/docs/deploying.rst
@@ -190,10 +190,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
 ---------------