Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.3.0
-
None
-
None
-
9: R&D, leftovers
-
1
Description
The cao tool when used with save/restore command, takes in the name of the CouchbaseCluster resource against which it would be executed.
This functionality can be achieved with the use of --cluster flag in the command.
However, the help section of the save/restore defines the flag incorrectly.
At the moment this flag is defined as:
Global Flags:
|
...
|
--cluster string The name of the kubeconfig cluster to use.
|
...
|
when it should have been "The name of the Couchbase cluster to use." and not present under Global Flags.
Observed Output:
Usage:
|
cao save [flags]
|
|
|
|
|
Examples:
|
# Save the full data topology on the only cluster in a namespace
|
cao save --filename save.yaml
|
|
# Save the full data topology for a specific cluster |
cao save --cluster cluster-name --filename save.yaml
|
|
# Save all scope and collections in a bucket
|
cao save --path /bucket --filename save.yaml
|
|
# Save all collections in a scope
|
cao save --path /bucket/scope --filename save.yaml
|
|
|
|
|
Flags:
|
-f, --filename string Filename to write the save data to. This flag is required.
|
-h, --help help for save |
--path string Path to save data from. Default will save all buckets, scopes and collections. '/bucket' will save all scopes and collection in Couchbase bucket 'bucket'. '/bucket/scope' will save all collections in Couchbase bucket 'bucket' and Couchbase scope 'scope'. (default "/") |
|
|
|
|
Global Flags:
|
...
|
--client-key string Path to a client key file for TLS |
--cluster string The name of the kubeconfig cluster to use
|
...
|
...
|