DOC-13542: Update Capella REST API builds for Morpheus

- [Template] Add tags to additional descriptions
- Build output documentation
- TEMP: Add preview config

Author: simon-dew

docs/modules/n1ql-rest-admin/pages/index.adoc

@@ -4988,9 +4988,11 @@ endif::alt-markdown-links[]
 The opaque ID or context provided by the client.
 If specified, all completed requests with this client context ID are logged.
 
+// tag::desc-more[]
 Refer to the [request-level][client_context_id] `client_context_id` parameter for more information.
 
 [client_context_id]: ../n1ql-rest-query/index.html#client_context_id
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -5718,9 +5720,11 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 The opaque ID or context provided by the client.
 
+// tag::desc-more[]
 Refer to the [request-level][client_context_id] `client_context_id` parameter for more information.
 
 [client_context_id]: ../n1ql-rest-query/index.html#client_context_id
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6202,10 +6206,12 @@ If any part of the path contains a special character, that part of the path must
 
 [additional-storage-use]: /server/8.0/learn/data/transactions.html#active-transaction-record-entries
 
+// tag::desc-more[]
 The [request-level][atrcollection_req] `atrcollection` parameter specifies this property per request.
 If a request does not include this parameter, the node-level `atrcollection` setting will be used.
 
 [atrcollection_req]: ../n1ql-rest-query/index.html#atrcollection_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6249,10 +6255,12 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 When enabled, the Query service preferentially aims to clean up just transactions that it has created, leaving transactions for the distributed cleanup process only when it is forced to.
 
+// tag::desc-more[]
 The [cluster-level][queryCleanupClientAttempts] `queryCleanupClientAttempts` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCleanupClientAttempts]: ../n1ql-rest-settings/index.html#queryCleanupClientAttempts
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6275,10 +6283,12 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 When enabled, the Query service takes part in the distributed cleanup process, and cleans up expired transactions created by any client.
 
+// tag::desc-more[]
 The [cluster-level][queryCleanupLostAttempts] `queryCleanupLostAttempts` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCleanupLostAttempts]: ../n1ql-rest-settings/index.html#queryCleanupLostAttempts
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6315,10 +6325,12 @@ Valid units are:
 
 [additional-storage-use]: /server/8.0/learn/data/transactions.html#active-transaction-record-entries
 
+// tag::desc-more[]
 The [cluster-level][queryCleanupWindow] `queryCleanupWindow` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCleanupWindow]: ../n1ql-rest-settings/index.html#queryCleanupWindow
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6363,10 +6375,12 @@ Refer to [Configure Completed Requests][sys-completed-config] for more informati
 
 [sys-completed-config]: ../n1ql/n1ql-manage/monitoring-n1ql-query.html#sys-completed-config
 
+// tag::desc-more[]
 The [cluster-level][queryCompletedLimit] `queryCompletedLimit` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCompletedLimit]: ../n1ql-rest-settings/index.html#queryCompletedLimit
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6397,10 +6411,12 @@ Refer to [Configure Completed Requests][sys-completed-config] for more informati
 
 [sys-completed-config]: ../n1ql/n1ql-manage/monitoring-n1ql-query.html#sys-completed-config
 
+// tag::desc-more[]
 The [cluster-level][queryCompletedMaxPlanSize] `queryCompletedMaxPlanSize` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCompletedMaxPlanSize]: ../n1ql-rest-settings/index.html#queryCompletedMaxPlanSize
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6456,10 +6472,12 @@ Refer to [Configure Completed Requests][sys-completed-config] for more informati
 
 [sys-completed-config]: ../n1ql/n1ql-manage/monitoring-n1ql-query.html#sys-completed-config
 
+// tag::desc-more[]
 The [cluster-level][queryCompletedThreshold] `queryCompletedThreshold` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryCompletedThreshold]: ../n1ql-rest-settings/index.html#queryCompletedThreshold
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6486,10 +6504,12 @@ When set to `true`, the query response document includes a controls section with
 
 NOTE: If the request qualifies for caching, these values will also be cached in the `completed_requests` system keyspace.
 
+// tag::desc-more[]
 The [request-level][controls_req] `controls` parameter specifies this property per request.
 If a request does not include this parameter, the node-level `controls` setting will be used.
 
 [controls_req]: ../n1ql-rest-query/index.html#controls_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6628,10 +6648,12 @@ Major items, like crashes.
 
 * `NONE` — Doesn't write anything.
 
+// tag::desc-more[]
 The [cluster-level][queryLogLevel] `queryLogLevel` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryLogLevel]: ../n1ql-rest-settings/index.html#queryLogLevel
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6682,6 +6704,7 @@ Refer to [Max Parallelism][max-parallelism] for more information.
 
 [max-parallelism]: ../n1ql/n1ql-language-reference/index-partitioning.html#max-parallelism
 
+// tag::desc-more[]
 The [cluster-level][queryMaxParallelism] `queryMaxParallelism` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -6692,6 +6715,7 @@ NOTE: To enable queries to run in parallel, you must specify the cluster-level `
 
 [queryMaxParallelism]: ../n1ql-rest-settings/index.html#queryMaxParallelism
 [max_parallelism_req]: ../n1ql-rest-query/index.html#max_parallelism_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6724,6 +6748,7 @@ It does not take into account any other memory that might be used to process a r
 Within a transaction, this setting enforces the memory quota for the transaction by tracking the
 delta table and the transaction log (approximately).
 
+// tag::desc-more[]
 The [cluster-level][queryMemoryQuota] `queryMemoryQuota` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -6732,6 +6757,7 @@ If a request includes this parameter, it will be capped by the node-level `memor
 
 [queryMemoryQuota]: ../n1ql-rest-settings/index.html#queryMemoryQuota
 [memory_quota_req]: ../n1ql-rest-query/index.html#memory_quota_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6794,10 +6820,12 @@ SQL++ feature control.
 This setting is provided for technical support only.
 The value may be an integer, or a string representing a hexadecimal number.
 
+// tag::desc-more[]
 The [cluster-level][queryN1QLFeatCtrl] `queryN1QLFeatCtrl` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryN1QLFeatCtrl]: ../n1ql-rest-settings/index.html#queryN1QLFeatCtrl
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6831,10 +6859,12 @@ To do this, the Query service calculates the difference between the total system
 
 - If the difference is 8 GiB or less, the default soft memory limit is set to 90% of the total system RAM.
 
+// tag::desc-more[]
 The [cluster-level][queryNodeQuota] `queryNodeQuota` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryNodeQuota]: ../n1ql-rest-settings/index.html#queryNodeQuota
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6857,10 +6887,12 @@ endif::alt-markdown-links[]
 The percentage of the `node-quota` that is dedicated to tracked value content memory across all active requests on this node.
 (The `memory-quota` setting specifies the maximum amount of document memory an individual request may use on this node.)
 
+// tag::desc-more[]
 The [cluster-level][queryNodeQuotaValPercent] `queryNodeQuotaValPercent` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryNodeQuotaValPercent]: ../n1ql-rest-settings/index.html#queryNodeQuotaValPercent
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6891,10 +6923,12 @@ The number of CPUs can never be greater than the number of logical CPUs.
 In Community Edition, the number of allowed CPUs cannot be greater than 4.
 In Enterprise Edition, there is no limit to the number of allowed CPUs.
 
+// tag::desc-more[]
 The [cluster-level][queryNumCpus] `queryNumCpus` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryNumCpus]: ../n1ql-rest-settings/index.html#queryNumCpus
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6919,6 +6953,7 @@ Specifies the total number of [active transaction records][additional-storage-us
 
 [additional-storage-use]: /server/8.0/learn/data/transactions.html#active-transaction-record-entries
 
+// tag::desc-more[]
 The [cluster-level][queryNumAtrs] `queryNumAtrs` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -6927,6 +6962,7 @@ The minimum of that and the node-level `numatrs` setting is applied.
 
 [queryNumAtrs]: ../n1ql-rest-settings/index.html#queryNumAtrs
 [numatrs_req]: ../n1ql-rest-query/index.html#numatrs_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6948,6 +6984,7 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 Controls the number of items execution operators can batch for Fetch from the KV.
 
+// tag::desc-more[]
 The [cluster-level][queryPipelineBatch] `queryPipelineBatch` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -6956,6 +6993,7 @@ The minimum of that and the node-level `pipeline-batch` setting is applied.
 
 [queryPipelineBatch]: ../n1ql-rest-settings/index.html#queryPipelineBatch
 [pipeline_batch_req]: ../n1ql-rest-query/index.html#pipeline_batch_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -6979,6 +7017,7 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 Maximum number of items each execution operator can buffer between various operators.
 
+// tag::desc-more[]
 The [cluster-level][queryPipelineCap] `queryPipelineCap` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -6987,6 +7026,7 @@ The minimum of that and the node-level `pipeline-cap` setting is applied.
 
 [queryPipelineCap]: ../n1ql-rest-settings/index.html#queryPipelineCap
 [pipeline_cap_req]: ../n1ql-rest-query/index.html#pipeline_cap_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7027,10 +7067,12 @@ endif::alt-markdown-links[]
 Maximum number of prepared statements in the cache.
 When this cache reaches the limit, the least recently used prepared statements will be discarded as new prepared statements are created.
 
+// tag::desc-more[]
 The [cluster-level][queryPreparedLimit] `queryPreparedLimit` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
 [queryPreparedLimit]: ../n1ql-rest-settings/index.html#queryPreparedLimit
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7053,10 +7095,12 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 Specifies whether query results are returned in pretty format.
 
+// tag::desc-more[]
 The [request-level][pretty_req] `pretty` parameter specifies this property per request.
 If a request does not include this parameter, the node-level setting is used, which defaults to `false`.
 
 [pretty_req]: ../n1ql-rest-query/index.html#pretty_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7094,10 +7138,12 @@ Refer to [Monitoring and Profiling Details][monitor-profile-details] for more in
 
 [monitor-profile-details]: ../n1ql/n1ql-manage/monitoring-n1ql-query.html#monitor-profile-details
 
+// tag::desc-more[]
 The [request-level][profile_req] `profile` parameter specifies this property per request.
 If a request does not include this parameter, the node-level `profile` setting will be used.
 
 [profile_req]: ../n1ql-rest-query/index.html#profile_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7143,6 +7189,7 @@ This parameter controls when to use scan backfill.
 Use `0` or a negative number to disable.
 Smaller values reduce GC, while larger values reduce indexer backfill.
 
+// tag::desc-more[]
 The [cluster-level][queryScanCap] `queryScanCap` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -7151,6 +7198,7 @@ The minimum of that and the node-level `scan-cap` setting is applied.
 
 [queryScanCap]: ../n1ql-rest-settings/index.html#queryScanCap
 [scan_cap_req]: ../n1ql-rest-query/index.html#scan_cap_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7198,6 +7246,7 @@ It must not be delimited by quotes, and must not include a unit.
 Specify `0` (the default value) or a negative integer to disable.
 When disabled, no timeout is applied and the request runs for however long it takes.
 
+// tag::desc-more[]
 The [cluster-level][queryTimeout] `queryTimeout` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -7206,6 +7255,7 @@ The minimum of that and the node-level `timeout` setting is applied.
 
 [queryTimeout]: ../n1ql-rest-settings/index.html#queryTimeout
 [timeout_req]: ../n1ql-rest-query/index.html#timeout_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7240,6 +7290,7 @@ When disabled, no timeout is applied and the transaction runs for however long i
 
 [tximplicit]: ../n1ql-rest-query/index.html#tximplicit
 
+// tag::desc-more[]
 The [cluster-level][queryTxTimeout] `queryTxTimeout` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -7248,6 +7299,7 @@ The minimum of that and the node-level `txtimeout` setting is applied.
 
 [queryTxTimeout]: ../n1ql-rest-settings/index.html#queryTxTimeout
 [txtimeout_req]: ../n1ql-rest-query/index.html#txtimeout_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7271,6 +7323,7 @@ ifdef::alt-markdown-links[]
 endif::alt-markdown-links[]
 Specifies whether the cost-based optimizer is enabled.
 
+// tag::desc-more[]
 The [cluster-level][queryUseCBO] `queryUseCBO` setting specifies this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is over-written for all nodes in the cluster.
 
@@ -7279,6 +7332,7 @@ If a request does not include this parameter, the node-level setting is used, wh
 
 [queryUseCBO]: ../n1ql-rest-settings/index.html#queryUseCBO
 [use_cbo_req]: ../n1ql-rest-query/index.html#use_cbo_req
+// end::desc-more[]
 --
 
 [%hardbreaks]
@@ -7317,6 +7371,7 @@ Reading from replica is only possible if the cluster uses Couchbase Server 7.6.0
 Note that KV range scans cannot currently be started on a replica vBucket.
 If a query uses sequential scan and a data node becomes unavailable, the query might return an error, even if read from replica is enabled for the request.
 
+// tag::desc-more[]
 The [cluster-level][queryUseReplica] `queryUseReplica` setting specifies the default for this property for the whole cluster.
 When you change the cluster-level setting, the node-level setting is overwritten for all nodes in the cluster.
 
@@ -7326,6 +7381,7 @@ If the request-level parameter and the node-level setting are both `unset`, read
 
 [queryUseReplica]: ../n1ql-rest-settings/index.html#queryUseReplica
 [use_replica_req]: ../n1ql-rest-query/index.html#use_replica_req
+// end::desc-more[]
 --
 
 [%hardbreaks]