review changes && update deps

Signed-off-by: Anisur Rahman <[email protected]>
kubedb · Sep 24, 2024 · 2f1c877 · 2f1c877
1 parent 73f5f4f
commit 2f1c877
Show file tree

Hide file tree

Showing 5 changed files with 11 additions and 12 deletions.
diff --git a/docs/guides/mysql/backup/kubestash/application-level/examples/restoresession.yaml b/docs/guides/mysql/backup/kubestash/application-level/examples/restoresession.yaml
@@ -5,9 +5,9 @@ metadata:
   namespace: demo
 spec:
   manifestOptions:
-    restoreNamespace: dev
     mySQL:
       db: true
+      restoreNamespace: dev
   dataSource:
     repository: gcs-mysql-repo
     snapshot: latest

diff --git a/docs/guides/mysql/backup/kubestash/application-level/index.md b/docs/guides/mysql/backup/kubestash/application-level/index.md
@@ -355,7 +355,7 @@ Let's create a secret called `encrypt-secret` with the Restic password,
 ```bash
 $ echo -n 'changeit' > RESTIC_PASSWORD
 $ kubectl create secret generic -n demo encrypt-secret \
-    --from-file=./RESTIC_PASSWORD \
+    --from-file=./RESTIC_PASSWORD
 secret "encrypt-secret" created
 ```
 
@@ -474,9 +474,9 @@ gcs-mysql-repo          true        1                806 B   Ready   8m27s
 At this moment we have one `Snapshot`. Run the following command to check the respective `Snapshot` which represents the state of a backup run for an application.
 
 ```bash
-$ kubectl get snapshots -n demo -l=kubestash.com/repo-name=gcs-demo-repo
+$ kubectl get snapshots -n demo -l=kubestash.com/repo-name=gcs-mysql-repo
 NAME                                                            REPOSITORY            SESSION           SNAPSHOT-TIME          DELETION-POLICY   PHASE       AGE
-gcs-mysql-repo-sample-mysql-backup-frequent-backup-1725359100   sample-mysql-backup   frequent-backup   2024-01-23T13:10:54Z   Delete            Succeeded   16h
+gcs-mysql-repo-sample-mysql-backup-frequent-backup-1725359100   gcs-mysql-repo        frequent-backup   2024-01-23T13:10:54Z   Delete            Succeeded   16h
 ```
 
 > Note: KubeStash creates a `Snapshot` with the following labels:
@@ -610,9 +610,9 @@ metadata:
   namespace: demo
 spec:
   manifestOptions:
-    restoreNamespace: dev
     mySQL:
       db: true
+      restoreNamespace: dev
   dataSource:
     repository: gcs-mysql-repo
     snapshot: latest

diff --git a/docs/guides/mysql/backup/kubestash/auto-backup/index.md b/docs/guides/mysql/backup/kubestash/auto-backup/index.md
@@ -130,7 +130,7 @@ Let's create a secret called `encrypt-secret` with the Restic password,
 ```bash
 $ echo -n 'changeit' > RESTIC_PASSWORD
 $ kubectl create secret generic -n demo encrypt-secret \
-    --from-file=./RESTIC_PASSWORD \
+    --from-file=./RESTIC_PASSWORD
 secret "encrypt-secret" created
 ```
 
@@ -329,7 +329,7 @@ Once a backup is complete, KubeStash will update the respective `Repository` CR
 
 ```bash
 $ kubectl get repository -n demo default-blueprint
-NAME                    INTEGRITY   SNAPSHOT-COUNT   SIZE    PHASE   LAST-SUCCESSFUL-BACKUP   AGE
+NAME                       INTEGRITY   SNAPSHOT-COUNT   SIZE    PHASE   LAST-SUCCESSFUL-BACKUP   AGE
 default-blueprint          true        1                806 B   Ready   8m27s                    9m18s
 ```
 

diff --git a/docs/guides/mysql/backup/kubestash/customization/index.md b/docs/guides/mysql/backup/kubestash/customization/index.md
@@ -281,7 +281,6 @@ spec:
 
 KubeStash also uses `mysql` during the restore process. In this section, we are going to show how you can pass arguments to the restore process, restore a specific snapshot, run restore job as a specific user, etc.
 
-
 ### Passing arguments to the restore process
 
 Similar to the backup process, you can pass arguments to the restore process through the `args` params under `addon.tasks[*].params` section. 
@@ -358,7 +357,7 @@ spec:
     name: restored-mysql
   dataSource:
     repository: gcs-mysql-repo
-    snapshot: latest
+    snapshot: gcs-mysql-repo-sample-mysql-backup-frequent-backup-1725257849
     encryptionSecret:
       name: encrypt-secret
       namespace: demo

diff --git a/docs/guides/mysql/backup/kubestash/logical/index.md b/docs/guides/mysql/backup/kubestash/logical/index.md
@@ -356,7 +356,7 @@ Let's create a secret called `encrypt-secret` with the Restic password,
 ```bash
 $ echo -n 'changeit' > RESTIC_PASSWORD
 $ kubectl create secret generic -n demo encrypt-secret \
-    --from-file=./RESTIC_PASSWORD \
+    --from-file=./RESTIC_PASSWORD
 secret "encrypt-secret" created
 ```
 
@@ -471,9 +471,9 @@ gcs-mysql-repo          true        1                806 B   Ready   8m27s
 At this moment we have one `Snapshot`. Run the following command to check the respective `Snapshot` which represents the state of a backup run for an application.
 
 ```bash
-$ kubectl get snapshots -n demo -l=kubestash.com/repo-name=gcs-demo-repo
+$ kubectl get snapshots -n demo -l=kubestash.com/repo-name=gcs-mysql-repo
 NAME                                                            REPOSITORY            SESSION           SNAPSHOT-TIME          DELETION-POLICY   PHASE       AGE
-gcs-mysql-repo-sample-mysql-backup-frequent-backup-1724065200   sample-mysql-backup   frequent-backup   2024-01-23T13:10:54Z   Delete            Succeeded   16h
+gcs-mysql-repo-sample-mysql-backup-frequent-backup-1724065200   gcs-mysql-repo        frequent-backup   2024-01-23T13:10:54Z   Delete            Succeeded   16h
 ```
 
 > Note: KubeStash creates a `Snapshot` with the following labels: