MB-34224 Merge branch 'spock' into vulcan

* spock:
  MB-34224 Correct doc for RBAC roles with multiple buckets
  MB-34224 Correct doc for RBAC roles with multiple buckets
  MB-31081 Generate missing documentation files
  MB-31083 Generate missing documentation files

Change-Id: I6d055fca7fbd9f405c90e46c56a9855432c1ea2a

Author: mcpaddy

docs/generated/doc/couchbase-cli/couchbase-cli-help.html

@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: couchbase-cli-help
 .\"    Author: Couchbase
-.\" Generator: Asciidoctor 1.5.7.1
-.\"      Date: 2018-08-29
+.\" Generator: Asciidoctor 2.0.9
+.\"      Date: 2019-06-11
 .\"    Manual: Couchbase CLI Manual
 .\"    Source: Couchbase CLI 1.0.0
 .\"  Language: English
 .\"
-.TH "COUCHBASE\-CLI\-HELP" "1" "2018-08-29" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
+.TH "COUCHBASE\-CLI\-HELP" "1" "2019-06-11" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -31,6 +31,7 @@
 couchbase\-cli\-help \- Show extended couchbase\-cli help
 .SH "SYNOPSIS"
 .sp
+.sp
 .nf
 \fIcouchbase\-cli help\fP
 .fi

docs/generated/doc/couchbase-cli/couchbase-cli-master-password.html

@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: couchbase-cli-master-password
 .\"    Author: Couchbase
-.\" Generator: Asciidoctor 1.5.7.1
-.\"      Date: 2018-08-29
+.\" Generator: Asciidoctor 2.0.9
+.\"      Date: 2019-06-12
 .\"    Manual: Couchbase CLI Manual
 .\"    Source: Couchbase CLI 1.0.0
 .\"  Language: English
 .\"
-.TH "COUCHBASE\-CLI\-MASTER\-PASSWORD" "1" "2018-08-29" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
+.TH "COUCHBASE\-CLI\-MASTER\-PASSWORD" "1" "2019-06-12" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -31,6 +31,7 @@
 couchbase\-cli\-master\-password \- Sends the Couchbase master password
 .SH "SYNOPSIS"
 .sp
+.sp
 .nf
 \fIcouchbase\-cli master\-password\fP [\-\-new\-password <password>]
 .fi

docs/generated/doc/couchbase-cli/couchbase-cli-server-eshell.html

@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: couchbase-cli-server-eshell
 .\"    Author: Couchbase
-.\" Generator: Asciidoctor 1.5.7.1
-.\"      Date: 2018-08-29
+.\" Generator: Asciidoctor 2.0.9
+.\"      Date: 2019-06-11
 .\"    Manual: Couchbase CLI Manual
 .\"    Source: Couchbase CLI 1.0.0
 .\"  Language: English
 .\"
-.TH "COUCHBASE\-CLI\-SERVER\-ESHELL" "1" "2018-08-29" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
+.TH "COUCHBASE\-CLI\-SERVER\-ESHELL" "1" "2019-06-11" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -31,6 +31,7 @@
 couchbase\-cli\-server\-eshell \- Opens a shell to talk to the cluster manager process
 .SH "SYNOPSIS"
 .sp
+.sp
 .nf
 \fIcouchbase\-cli server\-eshell\fP [\-\-cluster <url>] [\-\-username <user>]
     [\-\-password <password>] [\-\-vm <vm_name>] [\-\-erl <path>]

docs/generated/doc/couchbase-cli/couchbase-cli-user-manage.html

@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: couchbase-cli-user-manage
 .\"    Author: Couchbase
-.\" Generator: Asciidoctor 1.5.7.1
-.\"      Date: 2018-07-31
+.\" Generator: Asciidoctor 2.0.9
+.\"      Date: 2019-06-12
 .\"    Manual: Couchbase CLI Manual
 .\"    Source: Couchbase CLI 1.0.0
 .\"  Language: English
 .\"
-.TH "COUCHBASE\-CLI\-USER\-MANAGE" "1" "2018-07-31" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
+.TH "COUCHBASE\-CLI\-USER\-MANAGE" "1" "2019-06-12" "Couchbase CLI 1.0.0" "Couchbase CLI Manual"
 .ie \n(.g .ds Aq \(aq
 .el       .ds Aq '
 .ss \n[.ss] 0
@@ -31,6 +31,7 @@
 couchbase\-cli\-user\-manage \- Manage RBAC users
 .SH "SYNOPSIS"
 .sp
+.sp
 .nf
 \fIcouchbase\-cli user\-manage\fP [\-\-cluster <url>] [\-\-username <user>]
     [\-\-password <password>] [\-\-delete] [\-\-list] [\-\-my\-roles] [\-\-set]
@@ -190,7 +191,7 @@ a user the ability to manage all bucket settings set their role to
 bucket_admin[*]. To give the user permission to manage bucket settings on a
 single bucket named \fIdefault\fP then specify the role as
 bucket_admin[default]. If the user needs to be manage multiple buckets, for
-example \fIdefault\fP and \fIapp\fP, then set the role as bucket[default,app].
+example \fIdefault\fP and \fIapp\fP, then set the role as bucket[default],bucket[app].
 .RE
 .sp
 cluster_admin
@@ -222,7 +223,7 @@ all buckets set their role to views_admin[*]. To give the user permission to
 manage views on a single bucket named \fIdefault\fP then specify the role as
 views_admin[default]. If the user needs to be manage views for multiple
 buckets, for example \fIdefault\fP and \fIapp\fP, then set the role as
-views_admin[default,app].
+views_admin[default],views_admin[app].
 .RE
 .sp
 .B Data Service Roles:
@@ -235,7 +236,8 @@ To give a user read\-only access for all buckets set their role to
 data_reader[*]. To give the user read\-only access to data on a single
 bucket named \fIdefault\fP then specify their role as data_reader[default].
 If the user needs read\-only access to data for multiple buckets, for example
-\fIdefault\fP and \fIapp\fP, then set their role as data_reader[default,app].
+\fIdefault\fP and \fIapp\fP, then set their role as
+data_reader[default],data_reader[app].
 .RE
 .sp
 data_writer[...]
@@ -258,7 +260,7 @@ data_dcp_reader[*]. To give the user the ability to create DCP connections
 on a single bucket named \fIdefault\fP then specify their role as
 data_dcp_reader[default]. If the user needs to be able to create DCP
 connections for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set
-their role as data_dcp_reader[default,app].
+their role as data_dcp_reader[default],data_dcp_reader[app].
 .RE
 .sp
 data_backup[...]
@@ -269,7 +271,7 @@ to data_backup[*]. To give the user the ability to backup and restore data
 on a single bucket named \fIdefault\fP then specify their role as
 data_backup[default]. If the user needs to be able to backup and restore
 data for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their
-role as data_backup[default,app].
+role as data_backup[default],data_backup[app].
 .RE
 .sp
 data_monitoring[...]
@@ -280,7 +282,7 @@ buckets set their role to data_monitoring[*]. To give the user the ability
 to monitor data on a single bucket named \fIdefault\fP then specify their role
 as data_monitoring[default]. If the user needs to be able to monitor data
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as data_monitoring[default,app].
+as data_monitoring[default],data_monitoring[app].
 .RE
 .sp
 .B Full Text Service Roles:
@@ -294,7 +296,7 @@ on all buckets set their role to fts_admin[*]. To give the user full
 administrator access for FTS on a single bucket named \fIdefault\fP then specify
 their role as fts_admin[default]. If the user needs full administrator
 access for FTS for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then
-set their role as fts_admin[default,app].
+set their role as fts_admin[default],fts_admin[app].
 .RE
 .sp
 fts_searcher[...]
@@ -305,7 +307,7 @@ role to fts_searcher[*]. To give the ability to query FTS indexes on a
 single bucket named \fIdefault\fP then specify their role as
 fts_searcher[default]. If the user needs to query FTS indexes on multiple
 multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role as
-fts_searcher[default,app].
+fts_searcher[default],fts_searcher[app].
 .RE
 .sp
 .B Query Service Roles:
@@ -319,7 +321,7 @@ their role to manage_index[*]. To give the user permission to create and
 delete indexes on a single bucket named \fIdefault\fP then specify their role
 as manage_index[default]. If the user needs to be create and delete indexes
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as manage_index[default,app].
+as manage_index[default],manage_index[app].
 .RE
 .sp
 query_delete[...]
@@ -330,7 +332,7 @@ their role to query_delete[*]. To give the user permission to execute
 DELETE statements on a single bucket named \fIdefault\fP then specify their role
 as query_delete[default]. If the user needs to be execute DELETE statements
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as query_delete[default,app].
+as query_delete[default],query_delete[app].
 .RE
 .sp
 query_insert[...]
@@ -341,7 +343,7 @@ their role to query_insert[*]. To give the user permission to execute
 INSERT statements on a single bucket named \fIdefault\fP then specify their role
 as query_insert[default]. If the user needs to be execute INSERT statements
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as query_insert[default,app].
+as query_insert[default],query_insert[app].
 .RE
 .sp
 query_select[...]
@@ -352,7 +354,7 @@ their role to query_select[*]. To give the user permission to execute
 SELECT statements on a single bucket named \fIdefault\fP then specify their role
 as query_select[default]. If the user needs to be execute SELECT statements
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as query_select[default,app].
+as query_select[default],query_select[app].
 .RE
 .sp
 query_update[...]
@@ -363,7 +365,7 @@ their role to query_update[*]. To give the user permission to execute
 UPDATE statements on a single bucket named \fIdefault\fP then specify their role
 as query_update[default]. If the user needs to be execute UPDATE statements
 for multiple buckets, for example \fIdefault\fP and \fIapp\fP, then set their role
-as query_update[default,app].
+as query_update[default],query_update[app].
 .RE
 .sp
 system_catalog[...]
@@ -375,7 +377,7 @@ permission to run queries against the system catalog on a single bucket
 named \fIdefault\fP then specify their role as system_catalog[default]. If the
 user needs to be run queries against the system catalog for multiple
 buckets, for example \fIdefault\fP and \fIapp\fP, then set their role as
-system_catalog[default,app].
+system_catalog[default],system_catalog[app].
 .RE
 .SH "EXAMPLES"
 .sp

docs/generated/man/man1/couchbase-cli-help.1

@@ -88,7 +88,7 @@ bucket_admin[...]::
   bucket_admin[*]. To give the user permission to manage bucket settings on a
   single bucket named _default_ then specify the role as
   bucket_admin[default]. If the user needs to be manage multiple buckets, for
-  example _default_ and _app_, then set the role as bucket[default,app].
+  example _default_ and _app_, then set the role as bucket[default],bucket[app].
 
 cluster_admin::
   Gives the user permissions to read, write and manage all cluster-level
@@ -112,7 +112,7 @@ view_admin[...]::
   manage views on a single bucket named _default_ then specify the role as
   views_admin[default]. If the user needs to be manage views for multiple
   buckets, for example _default_ and _app_, then set the role as
-  views_admin[default,app].
+  views_admin[default],views_admin[app].
 
 .Data Service Roles:
 
@@ -122,7 +122,8 @@ data_reader[...]::
   data_reader[*]. To give the user read-only access to data on a single
   bucket named _default_ then specify their role as data_reader[default].
   If the user needs read-only access to data for multiple buckets, for example
-  _default_ and _app_, then set their role as data_reader[default,app].
+  _default_ and _app_, then set their role as
+  data_reader[default],data_reader[app].
 
 data_writer[...]::
   Gives the user permission to read and write data through Couchbases
@@ -141,7 +142,7 @@ data_dcp_reader[...]::
   on a single bucket named _default_ then specify their role as
   data_dcp_reader[default]. If the user needs to be able to create DCP
   connections for multiple buckets, for example _default_ and _app_, then set
-  their role as data_dcp_reader[default,app].
+  their role as data_dcp_reader[default],data_dcp_reader[app].
 
 data_backup[...]::
   Gives the user permission to backup and restore data in Couchbase. To give a
@@ -150,7 +151,7 @@ data_backup[...]::
   on a single bucket named _default_ then specify their role as
   data_backup[default]. If the user needs to be able to backup and restore
   data for multiple buckets, for example _default_ and _app_, then set their
-  role as data_backup[default,app].
+  role as data_backup[default],data_backup[app].
 
 data_monitoring[...]::
   Gives the user permission to read monitoring data related to the data
@@ -159,7 +160,7 @@ data_monitoring[...]::
   to monitor data on a single bucket named _default_ then specify their role
   as data_monitoring[default]. If the user needs to be able to monitor data
   for multiple buckets, for example _default_ and _app_, then set their role
-  as data_monitoring[default,app].
+  as data_monitoring[default],data_monitoring[app].
 
 .Full Text Service Roles:
 
@@ -170,7 +171,7 @@ fts_admin[...]::
   administrator access for FTS on a single bucket named _default_ then specify
   their role as fts_admin[default]. If the user needs full administrator
   access for FTS for multiple buckets, for example _default_ and _app_, then
-  set their role as fts_admin[default,app].
+  set their role as fts_admin[default],fts_admin[app].
 
 fts_searcher[...]::
   Allows the user to query full text indexes for the specified buckets. To
@@ -179,7 +180,7 @@ fts_searcher[...]::
   single bucket named _default_ then specify their role as
   fts_searcher[default]. If the user needs to query FTS indexes on multiple
   multiple buckets, for example _default_ and _app_, then set their role as
-  fts_searcher[default,app].
+  fts_searcher[default],fts_searcher[app].
 
 .Query Service Roles:
 
@@ -190,7 +191,7 @@ manage_index[...]::
   delete indexes on a single bucket named _default_ then specify their role
   as manage_index[default]. If the user needs to be create and delete indexes
   for multiple buckets, for example _default_ and _app_, then set their role
-  as manage_index[default,app].
+  as manage_index[default],manage_index[app].
 
 query_delete[...]::
   Allows the user to execute DELETE query statements on the specified buckets.
@@ -199,7 +200,7 @@ query_delete[...]::
   DELETE statements on a single bucket named _default_ then specify their role
   as query_delete[default]. If the user needs to be execute DELETE statements
   for multiple buckets, for example _default_ and _app_, then set their role
-  as query_delete[default,app].
+  as query_delete[default],query_delete[app].
 
 query_insert[...]::
   Allows the user to execute INSERT query statements on the specified buckets.
@@ -208,7 +209,7 @@ query_insert[...]::
   INSERT statements on a single bucket named _default_ then specify their role
   as query_insert[default]. If the user needs to be execute INSERT statements
   for multiple buckets, for example _default_ and _app_, then set their role
-  as query_insert[default,app].
+  as query_insert[default],query_insert[app].
 
 query_select[...]::
   Allows the user to execute SELECT query statements on the specified buckets.
@@ -217,7 +218,7 @@ query_select[...]::
   SELECT statements on a single bucket named _default_ then specify their role
   as query_select[default]. If the user needs to be execute SELECT statements
   for multiple buckets, for example _default_ and _app_, then set their role
-  as query_select[default,app].
+  as query_select[default],query_select[app].
 
 query_update[...]::
   Allows the user to execute UPDATE query statements on the specified buckets.
@@ -226,7 +227,7 @@ query_update[...]::
   UPDATE statements on a single bucket named _default_ then specify their role
   as query_update[default]. If the user needs to be execute UPDATE statements
   for multiple buckets, for example _default_ and _app_, then set their role
-  as query_update[default,app].
+  as query_update[default],query_update[app].
 
 system_catalog[...]::
   Allows the users to run queries against the system catalog on the specified
@@ -236,7 +237,7 @@ system_catalog[...]::
   named _default_ then specify their role as system_catalog[default]. If the
   user needs to be run queries against the system catalog for multiple
   buckets, for example _default_ and _app_, then set their role as
-  system_catalog[default,app].
+  system_catalog[default],system_catalog[app].
 
 == EXAMPLES