chore: Update manifests after change

clusters/cl01tl/manifests/grimmory/Deployment-grimmory.yaml

@@ -52,7 +52,7 @@ spec:
               valueFrom:
                 secretKeyRef:
                   key: password
-                  name: grimmory-database-config
+                  name: grimmory-database-secret
             - name: GRIMMORY_PORT
               value: "6060"
             - name: SWAGGER_ENABLED

clusters/cl01tl/manifests/grimmory/ExternalSecret-grimmory-database-secret.yaml

@@ -1,10 +1,10 @@
 apiVersion: external-secrets.io/v1
 kind: ExternalSecret
 metadata:
-  name: grimmory-database-config
+  name: grimmory-database-secret
   namespace: grimmory
   labels:
-    app.kubernetes.io/name: grimmory-database-config
+    app.kubernetes.io/name: grimmory-database-secret
     app.kubernetes.io/instance: grimmory
     app.kubernetes.io/part-of: grimmory
 spec:

clusters/cl01tl/manifests/grimmory/ExternalSecret-grimmory-mariadb-cluster-backup-secret-external.yaml

@@ -15,8 +15,8 @@ spec:
     - secretKey: access
       remoteRef:
         key: /digital-ocean/home-infra/mariadb-backups
-        property: access
+        property: AWS_ACCESS_KEY_ID
     - secretKey: secret
       remoteRef:
         key: /digital-ocean/home-infra/mariadb-backups
-        property: secret
+        property: AWS_SECRET_ACCESS_KEY

clusters/cl01tl/manifests/grimmory/MariaDB-grimmory-mariadb-cluster.yaml

@@ -31,6 +31,6 @@ spec:
   rootPasswordSecretKeyRef:
     generate: false
     key: password
-    name: grimmory-database-config
+    name: grimmory-database-secret
   storage:
     size: 5Gi