From 021aff1fc7954cdc3ed650b550b0fac989fa51d5 Mon Sep 17 00:00:00 2001
From: Leon <82407168+sed-i@users.noreply.github.com>
Date: Tue, 27 Aug 2024 18:01:29 -0400
Subject: [PATCH] Use the name variable for placeholder container, resource
 names

---
 charmcraft/templates/init-kubernetes/charmcraft.yaml.j2 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/charmcraft/templates/init-kubernetes/charmcraft.yaml.j2 b/charmcraft/templates/init-kubernetes/charmcraft.yaml.j2
index e87a3599a..6f4dcc833 100644
--- a/charmcraft/templates/init-kubernetes/charmcraft.yaml.j2
+++ b/charmcraft/templates/init-kubernetes/charmcraft.yaml.j2
@@ -60,17 +60,17 @@ config:
 
 # Your workload’s containers.
 containers:
-  some-container:
-    resource: some-container-image
+  {{ name }}:
+    resource: {{ name }}-image
 
 
 # This field populates the Resources tab on Charmhub.
 resources:
   # An OCI image resource for each container listed above.
   # You may remove this if your charm will run without a workload sidecar container.
-  some-container-image:
+  {{ name }}-image:
     type: oci-image
-    description: OCI image for the 'some-container' container
+    description: OCI image for the {{ name }} container
     # The upstream-source field is ignored by Juju. It is included here as a reference
     # so the integration testing suite knows which image to deploy during testing. This field
     # is also used by the 'canonical/charming-actions' Github action for automated releasing.