fixing safe-content api name

0xIntuition · Dec 19, 2024 · 4cf572d · 4cf572d
1 parent 3b6ac19
commit 4cf572d
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 8 deletions.
diff --git a/devops/aws/safe-content-api/deployment.yaml b/devops/aws/safe-content-api/deployment.yaml
@@ -1,19 +1,19 @@
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: safe-content-api
+  name: safe-content
 spec:
   selector:
     matchLabels:
-      io.kompose.service: safe-content-api
+      io.kompose.service: safe-content
   template:
     metadata:
       labels:
-        io.kompose.service: safe-content-api
+        io.kompose.service: safe-content
     spec:
       serviceAccountName: secrets-access-sa
       containers:
-        - name: safe-content-api
+        - name: safe-content
           image: steelcityamir/safe-content-ai:latest
           imagePullPolicy: Always 
           ports:

diff --git a/devops/aws/safe-content-api/service.yaml b/devops/aws/safe-content-api/service.yaml
@@ -5,13 +5,13 @@ metadata:
     kompose.cmd: kompose convert -f docker-compose-kompose.yml
     kompose.version: 1.34.0 (HEAD)
   labels:
-    io.kompose.service: safe-content-api
-  name: safe-content-api
+    io.kompose.service: safe-content
+  name: safe-content
 spec:
   type: ClusterIP 
   ports:
     - name: "8000"
       port: 8000
       targetPort: 8000
   selector:
-    io.kompose.service: safe-content-api
+    io.kompose.service: safe-content
diff --git a/devops/minikube/services/graphql/deployment.yaml b/devops/minikube/services/graphql/deployment.yaml
@@ -46,7 +46,7 @@ spec:
               valueFrom:
                 secretKeyRef:
                   name: secrets
-                  key: PINATA_API_JWT
+                  key: PINATA_AUTH
           image: hasura/graphql-engine:v2.44.0
           livenessProbe:
             exec: