Skip to content

Commit

Permalink
Fix BackupSession's Print Columns (#9)
Browse files Browse the repository at this point in the history
  • Loading branch information
hossainemruz authored and tamalsaha committed Oct 23, 2019
1 parent 201a06e commit 1c447f4
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 9 deletions.
6 changes: 3 additions & 3 deletions docs/mongodb-replicaset.md
Original file line number Diff line number Diff line change
Expand Up @@ -405,9 +405,9 @@ Wait for the next schedule. Run the following command to watch `BackupSession` c

```console
$ kubectl get backupsession -n demo -w
NAME BACKUPCONFIGURATION PHASE AGE
sample-mgo-rs-backup-1563540308 sample-mgo-rs-backup Running 5m19s
sample-mgo-rs-backup-1563540308 sample-mgo-rs-backup Succeeded 5m45s
NAME INVOKER-TYPE INVOKER-NAME PHASE AGE
sample-mgo-rs-backup-1563540308 BackupConfiguration sample-mgo-rs-backup Running 5m19s
sample-mgo-rs-backup-1563540308 BackupConfiguration sample-mgo-rs-backup Succeeded 5m45s
```

We can see above that the backup session has succeeded. Now, we are going to verify that the backed up data has been stored in the backend.
Expand Down
6 changes: 3 additions & 3 deletions docs/mongodb-sharding.md
Original file line number Diff line number Diff line change
Expand Up @@ -431,9 +431,9 @@ Wait for the next schedule. Run the following command to watch `BackupSession` c

```console
$ kubectl get backupsession -n demo -w
NAME BACKUPCONFIGURATION PHASE AGE
sample-mgo-sh-backup-1563512707 sample-mgo-sh-backup Running 5m19s
sample-mgo-sh-backup-1563512707 sample-mgo-sh-backup Succeeded 5m45s
NAME INVOKER-TYPE INVOKER-NAME PHASE AGE
sample-mgo-sh-backup-1563512707 BackupConfiguration sample-mgo-sh-backup Running 5m19s
sample-mgo-sh-backup-1563512707 BackupConfiguration sample-mgo-sh-backup Succeeded 5m45s
```

We can see above that the backup session has succeeded. Now, we are going to verify that the backed up data has been stored in the backend.
Expand Down
6 changes: 3 additions & 3 deletions docs/mongodb.md
Original file line number Diff line number Diff line change
Expand Up @@ -406,9 +406,9 @@ Wait for the next schedule. Run the following command to watch `BackupSession` c

```console
$ kubectl get backupsession -n demo -w
NAME BACKUPCONFIGURATION PHASE AGE
sample-mongodb-backup-1561974001 sample-mongodb-backup Running 5m19s
sample-mongodb-backup-1561974001 sample-mongodb-backup Succeeded 5m45s
NAME INVOKER-TYPE INVOKER-NAME PHASE AGE
sample-mongodb-backup-1561974001 BackupConfiguration sample-mongodb-backup Running 5m19s
sample-mongodb-backup-1561974001 BackupConfiguration sample-mongodb-backup Succeeded 5m45s
```

We can see above that the backup session has succeeded. Now, we are going to verify that the backed up data has been stored in the backend.
Expand Down

0 comments on commit 1c447f4

Please sign in to comment.