updating readme with command changes and chaning slv-operator package…

… name
amagioss · Mar 4, 2024 · 2da1d62 · 2da1d62
1 parent d6e7084
commit 2da1d62
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 7 deletions.
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
@@ -55,6 +55,6 @@ jobs:
           context: .
           push: true
           tags: |
-            ghcr.io/${{ github.repository }}/operator:${{ env.SLV_VERSION }}
-            ghcr.io/${{ github.repository }}/operator:${{ github.ref_name }}
-            ghcr.io/${{ github.repository }}/operator:latest
+            ghcr.io/${{ github.repository }}/slv-operator:${{ env.SLV_VERSION }}
+            ghcr.io/${{ github.repository }}/slv-operator:${{ github.ref_name }}
+            ghcr.io/${{ github.repository }}/slv-operator:latest
diff --git a/README.md b/README.md
@@ -56,7 +56,7 @@ Created vault: test.slv.yaml
 
 #### Add secrets to the vault
 ```sh
-$ slv secret put -v test.slv.yaml -n db_password -s "super_secret_pwd"
+$ slv vault put -v test.slv.yaml -n db_password -s "super_secret_pwd"
 
 Added secret: db_password to vault: test.slv.yaml
 ```
@@ -65,7 +65,7 @@ Added secret: db_password to vault: test.slv.yaml
 Set the environment variable `SLV_ENV_SECRET_KEY` to the secret key generated in the previous step
 ```sh
 $ export SLV_ENV_SECRET_KEY=SLV_ESK_AEAEKAHBIONE3QIIWFXFRNJPE6A6AYL527QW4OF4HWWFDOE5E4XR5LO2WI
-$ slv secret get -v test.slv.yaml -n db_password
+$ slv vault get -v test.slv.yaml -n db_password
 
 super_secret_pwd
 ```

diff --git a/operator/README.md b/operator/README.md
@@ -26,7 +26,7 @@ kubectl get secret pets -o jsonpath='{.data.supercat}' | base64 --decode
 ```
 - Add any secret using the following commands
 ```sh
-slv secret put -v pets.slv.yaml -n hi -s "Hello World"
+slv vault put -v pets.slv.yaml -n hi -s "Hello World"
 kubectl apply -f pets.slv.yaml
 ```
 - Try reading newly created secret from the cluster

diff --git a/operator/deploy.yaml b/operator/deploy.yaml
@@ -145,7 +145,7 @@ spec:
       serviceAccountName: slv-operator
       containers:
       - name: slv-operator
-        image: ghcr.io/savesecrets/slv/operator:latest # Use a specific version tag corresponding to the version of SLV used with the CR
+        image: ghcr.io/savesecrets/slv/slv-operator:latest # Use a specific version tag corresponding to the version of SLV used with the CR
         resources:
           limits:
             cpu: "1" # 1 CPU should be fairly enough for SLV Controller