New upgrade implementation (#418)

## Issue Current upgrade implementation should be replaced with v2 ## Solution Replace current upgrade implementation with v2 --------- Co-authored-by: Carl Csaposs <[email protected]> Co-authored-by: Mehdi Bendriss <[email protected]>
canonical · Jun 11, 2024 · eb9c9e0 · eb9c9e0
1 parent d67c815
commit eb9c9e0
Show file tree

Hide file tree

Showing 31 changed files with 1,506 additions and 1,788 deletions.
diff --git a/actions.yaml b/actions.yaml
@@ -57,4 +57,10 @@ set-tls-private-key:
       description: The content of private key for internal communications with clients. Content will be auto-generated if this option is not specified.
 
 pre-upgrade-check:
-  description: Run necessary pre-upgrade checks before executing a charm upgrade.
+  description: Check if charm is ready to upgrade
+
+resume-upgrade:
+  description: Upgrade remaining units (after you manually verified that upgraded units are healthy).
+
+force-upgrade:
+  description: Force upgrade of this unit.
diff --git a/charm_version b/charm_version
@@ -0,0 +1 @@
+1
diff --git a/charmcraft.yaml b/charmcraft.yaml
@@ -20,3 +20,6 @@ parts:
       - libssl-dev
       - rustc
       - cargo
+    prime:
+      - charm_version
+      - workload_version