From a048704ed3f92fd81a3e548c6eebab637ee2c54f Mon Sep 17 00:00:00 2001 From: "Md. Emruz Hossain" Date: Tue, 22 Oct 2019 22:15:40 +0600 Subject: [PATCH] Fix BackupSession's Print Columns (#9) --- docs/mongodb-replicaset.md | 6 +++--- docs/mongodb-sharding.md | 6 +++--- docs/mongodb.md | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/mongodb-replicaset.md b/docs/mongodb-replicaset.md index 6c94bf559..2f049828b 100644 --- a/docs/mongodb-replicaset.md +++ b/docs/mongodb-replicaset.md @@ -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. diff --git a/docs/mongodb-sharding.md b/docs/mongodb-sharding.md index 623b1bb31..6c2e1f709 100644 --- a/docs/mongodb-sharding.md +++ b/docs/mongodb-sharding.md @@ -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. diff --git a/docs/mongodb.md b/docs/mongodb.md index 5b7a60141..a9ab76697 100644 --- a/docs/mongodb.md +++ b/docs/mongodb.md @@ -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.