patch: move Glide to the requirer charm

src/events/base_events.py

@@ -33,7 +33,7 @@
     Substrate,
     TLSState,
 )
-from statuses import CharmStatuses, ClusterStatuses, ScaleDownStatuses, StartStatuses
+from statuses import CharmStatuses, ClusterStatuses, ScaleDownStatuses
 
 if TYPE_CHECKING:
     from charm import ValkeyCharm
@@ -197,11 +197,8 @@ def _on_start(self, event: ops.StartEvent) -> None:
             event.defer()
             return
 
-        self.charm.status.set_running_status(
-            StartStatuses.SERVICE_STARTING.value,
-            scope="unit",
-            statuses_state=self.charm.state.statuses,
-            component_name=self.charm.cluster_manager.name,
+        self.charm.state.unit_server.update(
+            {"start_state": StartState.STARTING_WAITING_VALKEY.value}
         )
         self.unit_fully_started.emit(
             is_primary=primary_endpoint

src/managers/cluster.py

@@ -128,7 +128,11 @@ def reload_tls_settings(self, tls_config: dict[str, str]) -> None:
 
     def get_statuses(self, scope: Scope, recompute: bool = False) -> list[StatusObject]:
         """Compute the cluster manager's statuses."""
-        status_list: list[StatusObject] = []
+        status_list: list[StatusObject] = self.state.statuses.get(
+            scope=scope,
+            component=self.name,
+            running_status_only=True,
+        ).root
 
         # Peer relation not established yet, or model not built yet for unit or app
         if not self.state.cluster.model or not self.state.unit_server.model:

src/managers/tls.py

@@ -438,14 +438,14 @@ def get_statuses(self, scope: Scope, recompute: bool = False) -> list[StatusObje
         ):
             status_list.append(TLSStatuses.DISABLING_CLIENT_TLS_FAILED.value)
 
-        if self.state.cluster.tls_client_private_key and not self.state.client_tls_relation:
-            status_list.append(TLSStatuses.PRIVATE_KEY_BUT_NO_TLS.value)
-
         if (
             private_key_id := self.state.config.get(TLS_CLIENT_PRIVATE_KEY_CONFIG)
         ) and self.read_and_validate_private_key(str(private_key_id)) is None:
             status_list.append(TLSStatuses.PRIVATE_KEY_INVALID.value)
 
+        if self.state.cluster.tls_client_private_key and not self.state.client_tls_relation:
+            status_list.append(TLSStatuses.PRIVATE_KEY_BUT_NO_TLS.value)
+
         if self.state.unit_server.tls_client_state == TLSState.TO_NO_TLS:
             status_list.append(TLSStatuses.DISABLING_CLIENT_TLS.value)
 

src/statuses.py

@@ -63,7 +63,6 @@ class StartStatuses(Enum):
     SERVICE_STARTING = StatusObject(
         status="maintenance",
         message="Waiting for Valkey to start...",
-        running="async",
     )
     WAITING_FOR_SENTINEL_DISCOVERY = StatusObject(
         status="maintenance",

src/workload_vm.py

@@ -93,6 +93,9 @@ def install(self, revision: str | None = None, retry_and_raise: bool = True) ->
             revision = str(SNAP_REVISIONS[platform.machine()])
 
         try:
+            # TODO revesit this logic after snapd update is released
+            # refresh snapd to use candidate to bypass risv check issue.
+            snap.add("snapd", channel="candidate")
             # as long as 26.04 is not stable, we need to install the core26 snap from beta
             snap.add("core26", channel="beta")
 

tests/integration/clients/requirer-charm/charmcraft.yaml

@@ -103,20 +103,109 @@ actions:
         description: The username to use
         type: string
 
+  execute:
+    description: Execute an arbitrary Valkey command through the Glide client
+    params:
+      command:
+        description: The Valkey command to execute (e.g. "PING", "SET key value", "GET key")
+        type: string
+      config:
+        description: >
+          Serialized GlideClientConfiguration JSON produced by
+          glide_helpers.serialize_glide_config(). The charm connects using this
+          configuration directly, independent of any relation or glide-config
+          option.
+        type: string
+
   get-credentials:
     description: Action for fetching all available credentials from relations.
 
+  start-continuous-writes:
+    description: >
+      Start a background daemon that continuously writes incrementing integers
+      to a Valkey list using the relation-provided credentials. The daemon
+      survives between action calls and can be stopped with
+      stop-continuous-writes.
+    params:
+      sleep-interval:
+        description: Seconds to sleep between writes (float, default 1.0)
+        type: number
+        default: 1.0
+      clear-existing:
+        description: Delete any existing list values before starting (default true)
+        type: boolean
+        default: true
+
+  get-continuous-writes-state:
+    description: >
+      Return the last written value and total count from the continuous-writes
+      state file without stopping the daemon.
+
+  assert-continuous-writes-increasing:
+    description: >
+      Assert that the continuous-writes daemon is actively writing by sampling
+      the state file twice with a configurable wait between samples and
+      verifying the count has increased.
+    params:
+      wait:
+        description: Seconds to wait between the two state samples (default 10)
+        type: number
+        default: 10
+
+  clear-continuous-writes:
+    description: >
+      Delete the continuous-writes key from Valkey. Can be run while the daemon
+      is stopped to reset data between test runs.
+
+  stop-continuous-writes:
+    description: >
+      Stop the continuous-writes daemon and return the last written value and
+      total count of successful writes. Use this after a disruptive operation to
+      retrieve stats for consistency verification.
+    params:
+      clear:
+        description: Delete continuous-writes data from Valkey after stopping (default
+          false)
+        type: boolean
+        default: false
+
+  seed-data:
+    description: >
+      Seed Valkey with random 1 KB values using the relation-provided
+      credentials. Keys are written in batches of 5000 using MSET and named
+      "<key-prefix><index>".
+    params:
+      target-gb:
+        description: Target amount of data to seed in GB (default 1.0)
+        type: number
+        default: 1.0
+      key-prefix:
+        description: Prefix for generated keys (default "seed:key:")
+        type: string
+        default: "seed:key:"
+
 config:
   options:
     data-interfaces-version:
       description: Version of data interfaces to use
       type: int
       default: 1
+    glide-config:
+      description: >
+        JSON string with Glide connection options. When set, the charm uses
+        config-based connection instead of the Valkey relation. Expected keys:
+        endpoints (comma-separated "host:port" string), username (string),
+        password (string), tls_enabled (bool), cacert (base64-encoded PEM CA
+        certificate string), cert (base64-encoded PEM client certificate
+        string), key (base64-encoded PEM client private key string).
+      type: string
+      default: ""
     use-mtls:
       description: Flag to enable use of mutual TLS
       type: boolean
       default: false
     use-certificate-auth:
-      description: Flag to enable authentication via the common name of the client certificate
+      description: Flag to enable authentication via the common name of the client
+        certificate
       type: boolean
       default: false