From ea56d1b370566a56c25777b8d7ea83fd4d4d6c42 Mon Sep 17 00:00:00 2001 From: Smail KOURTA Date: Tue, 21 Apr 2026 18:09:40 +0400 Subject: [PATCH 1/2] update rock in metadata Signed-off-by: Smail KOURTA --- metadata.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/metadata.yaml b/metadata.yaml index f45dbea..e76f486 100644 --- a/metadata.yaml +++ b/metadata.yaml @@ -30,7 +30,7 @@ resources: valkey-image: type: oci-image description: OCI Image for Valkey - upstream-source: ghcr.io/canonical/valkey:9.0.1-26.04-edge + upstream-source: ghcr.io/canonical/charmed-valkey:9.0.1-26.04_edge peers: valkey-peers: From aaade4daa6d1f430ab854fb5a483a2f3ef51b9a7 Mon Sep 17 00:00:00 2001 From: Smail KOURTA Date: Tue, 21 Apr 2026 15:17:27 +0100 Subject: [PATCH 2/2] fix the same in contributing md file --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c40bd04..7e6d92e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -58,7 +58,7 @@ in Juju. For details, see [development setup](https://documentation.ubuntu.com/j In our case, we want to deploy `valkey` to a model `test` on a Kubernetes cloud. Use the `upstream-source` from `metadata.yaml`: ```shell -$ juju deploy ./valkey_ubuntu@24.04-amd64.charm -n 3 --resource valkey-image=ghcr.io/canonical/valkey:9.0.1-26.04-edge --trust +$ juju deploy ./valkey_ubuntu@24.04-amd64.charm -n 3 --resource valkey-image=ghcr.io/canonical/charmed-valkey:9.0.1-26.04_edge --trust $ juju status Model Controller Cloud/Region Version SLA Timestamp