From dc79ad95716ca1c6e1f26db2fd84b86a25be68ec Mon Sep 17 00:00:00 2001 From: ibsoln <52778946+ibsoln@users.noreply.github.com> Date: Fri, 11 Feb 2022 09:07:48 +0000 Subject: [PATCH] QF220211-1 -- Sweep to remove beta references --- .../attachments/configuration-properties-legacy.yaml | 8 ++++---- modules/ROOT/pages/_partials/_page-index.adoc | 4 ++-- modules/ROOT/pages/_partials/_related-content.adoc | 2 +- modules/ROOT/pages/_partials/_stats-item-names.adoc | 2 +- modules/ROOT/pages/_partials/block-caveats.adoc | 4 ++-- .../ROOT/pages/_partials/common-cfg-ext-javascript.adoc | 4 ++-- modules/ROOT/pages/_partials/common-releasenotes.adoc | 2 +- modules/ROOT/pages/_partials/compatibility-cbl-sgw.adoc | 4 ++-- modules/ROOT/pages/_partials/concepts/sync-function.adoc | 2 +- .../definitions/database_configuration_model.adoc | 4 ++-- .../_partials/howto/how-to-assign-users-to-roles.adoc | 2 +- .../_partials/howto/how-to-control-document-access.adoc | 8 ++++---- .../ROOT/pages/_partials/howto/how-to-create-roles.adoc | 2 +- .../ROOT/pages/_partials/howto/how-to-create-users.adoc | 2 +- .../howto/how-to-use-xattrs-for-access-grants.adoc | 2 +- modules/ROOT/pages/_partials/sgw-svr-compatibility.adoc | 6 +++--- modules/ROOT/pages/_partials/sync-function-ovw.adoc | 2 +- .../access-control-how-use-xattrs-for-access-grants.adoc | 2 +- modules/ROOT/pages/access-control-how.adoc | 4 ++-- modules/ROOT/pages/configuration-overview.adoc | 4 ++-- modules/ROOT/pages/configuration-properties-legacy.adoc | 8 ++++---- modules/ROOT/pages/configuration-schema-database.adoc | 2 +- modules/ROOT/pages/configuration-schema-db-security.adoc | 2 +- modules/ROOT/pages/configuration-schema-isgr.adoc | 2 +- modules/ROOT/pages/get-started-install.adoc | 6 ++---- modules/ROOT/pages/logging.adoc | 2 +- modules/ROOT/pages/secure-sgw-access.adoc | 2 +- modules/ROOT/pages/upgrading.adoc | 8 ++++---- 28 files changed, 50 insertions(+), 52 deletions(-) diff --git a/modules/ROOT/assets/attachments/configuration-properties-legacy.yaml b/modules/ROOT/assets/attachments/configuration-properties-legacy.yaml index 941eb04f0..955f8aef0 100644 --- a/modules/ROOT/assets/attachments/configuration-properties-legacy.yaml +++ b/modules/ROOT/assets/attachments/configuration-properties-legacy.yaml @@ -7,7 +7,7 @@ properties: type: boolean default: 'true' description: |+ - Use `admin_interface_authentication=false` to turn of the secure remote administration feature introduced in 3.0 BETA. + Use `admin_interface_authentication=false` to turn of the secure remote administration feature introduced in 3.0. This is on by default and requires Couchbase Server RBAC-users to authenticate Admin API access. adminUI: @@ -30,7 +30,7 @@ properties: type: boolean default: 'true' description: |+ - Use `metrics_interface_authentication=false` to turn of the secure remote administration feature introduced in 3.0 BETA. + Use `metrics_interface_authentication=false` to turn of the secure remote administration feature introduced in 3.0. This is on by default and requires Couchbase Server RBAC-users to authenticate Metrics API access. @@ -893,7 +893,7 @@ properties: **Options** - Your replications can be one of two available types -- see [replication types](./../learn/icr-replication-types.html) (not available in beta) + Your replications can be one of two available types -- see [replication types](./../learn/icr-replication-types.html - Persistent -- the replication survives node restarts. These replications can also be launched dynamically using the Rest API `_replication` endpoint (see -- [Admin Rest API](./../refer/rest-api-admin.html)) @@ -1340,7 +1340,7 @@ properties: type: boolean default: 'false' description: |+ - Set to true to disable the persistent configuration handling introduced in 3.0 BETA + Set to true to disable the persistent configuration handling introduced in 3.0 facebook: description: Configuration for Facebook Login authentication. type: object diff --git a/modules/ROOT/pages/_partials/_page-index.adoc b/modules/ROOT/pages/_partials/_page-index.adoc index 92cad3da3..0c6c6bf20 100644 --- a/modules/ROOT/pages/_partials/_page-index.adoc +++ b/modules/ROOT/pages/_partials/_page-index.adoc @@ -445,7 +445,7 @@ endif::xref--pfx-sgw[] :configuration-schema-database--pfx--oidc: {configuration-schema-database--pfx--db}-oidc :configuration-schema-database--pfx--eventhandlers-doc-changed: {configuration-schema-database--pfx--eventhandlers}-document_changed -// :configuration-schema-database--xref: {configuration-schema-database--pfx}[Legacy Pre-3.0 BETA Configuration] +// :configuration-schema-database--xref: {configuration-schema-database--pfx}[Legacy Pre-3.0 Configuration] :configuration-schema-database--xref--allow-conflicts: {configuration-schema-database--pfx--db}-allow_conflicts[allow_conflicts] :configuration-schema-database--xref--bucket: {configuration-schema-database--pfx--db}-bucket[database_bucket] @@ -520,7 +520,7 @@ endif::xref--pfx-sgw[] :configuration-properties-legacy--pfx--databases-oidc: {configuration-properties-legacy--pfx--db}-this_db-oidc :configuration-properties-legacy--pfx--eventhandlers-doc-changed: {configuration-properties-legacy--pfx--eventhandlers}-document_changed -:configuration-properties-legacy--xref: {configuration-properties-legacy--pfx}[Legacy Pre-3.0 BETA Configuration] +:configuration-properties-legacy--xref: {configuration-properties-legacy--pfx}[Legacy Pre-3.0 Configuration] // :configuration-properties-legacy--xref-use_tls_sever: {configuration-properties-legacy--pfx}#use_tls_sever[use_tls_sever] :configuration-properties-legacy--xref-disable-persistent-config: {configuration-properties-legacy--pfx}#disable_persistent_config[disable-persistent-config] diff --git a/modules/ROOT/pages/_partials/_related-content.adoc b/modules/ROOT/pages/_partials/_related-content.adoc index 91b17b9d3..e5fe2d4c1 100644 --- a/modules/ROOT/pages/_partials/_related-content.adoc +++ b/modules/ROOT/pages/_partials/_related-content.adoc @@ -53,7 +53,7 @@ * xref:configuration-schema-access-control.adoc[Access Control] * xref:configuration-schema-import-filter.adoc[Import Filter] * xref:configuration-schema-isgr.adoc[Inter-Sync{nbsp}Gateway Replication] - * xref:configuration-properties-legacy.adoc[Legacy Pre-3.0 BETA Configuration] + * xref:configuration-properties-legacy.adoc[Legacy Pre-3.0 Configuration] // end::reference-config[] diff --git a/modules/ROOT/pages/_partials/_stats-item-names.adoc b/modules/ROOT/pages/_partials/_stats-item-names.adoc index 871d9672b..988b6565f 100644 --- a/modules/ROOT/pages/_partials/_stats-item-names.adoc +++ b/modules/ROOT/pages/_partials/_stats-item-names.adoc @@ -151,7 +151,7 @@ :sgr_docs_checked_sent: {xref-cb-config}sgr_docs_checked_sent[sgr_docs_checked_sent] // end::sgr1-replication-stats[] -// Pre beta values, no longer included in sgr2 and-or renamed +// Pre values, no longer included in sgr2 and-or renamed :sgr_num_attachment_bytes_transferred: {xref-cb-config}sgr_num_attachment_bytes_transferred[sgr_num_attachment_bytes_transferred] :sgr_num_attachments_transferred: {xref-cb-config}sgr_num_attachments_transferred[sgr_num_attachments_transferred] diff --git a/modules/ROOT/pages/_partials/block-caveats.adoc b/modules/ROOT/pages/_partials/block-caveats.adoc index 5a5415912..3950614bd 100644 --- a/modules/ROOT/pages/_partials/block-caveats.adoc +++ b/modules/ROOT/pages/_partials/block-caveats.adoc @@ -137,10 +137,10 @@ Do not use the `logs` directory as a storage location for files that should not ifndef::no-admonition[] [{caveat-level}] -- -Persistent Configuration is enabled by default from 3.0 BETA. +Persistent Configuration is enabled by default from 3.0. endif::no-admonition[] -To continue using legacy Pre-3.0 BETA configuration you should start {sgw} with {configuration-properties-legacy--xref-disable-persistent-config} set `true` either in the configuration file or in {command-line-options--xref}. +To continue using legacy Pre-3.0 configuration you should start {sgw} with {configuration-properties-legacy--xref-disable-persistent-config} set `true` either in the configuration file or in {command-line-options--xref}. ifndef::no-admonition[] -- diff --git a/modules/ROOT/pages/_partials/common-cfg-ext-javascript.adoc b/modules/ROOT/pages/_partials/common-cfg-ext-javascript.adoc index 9d12c7432..ae8179736 100644 --- a/modules/ROOT/pages/_partials/common-cfg-ext-javascript.adoc +++ b/modules/ROOT/pages/_partials/common-cfg-ext-javascript.adoc @@ -8,7 +8,7 @@ // Requires -- partial$_page-index.adoc attributes // End -- Inclusion Definition // Begin -- Inclusion Content -:fn-3x0: footnote:fn30[Commencing with release 3.0 BETA] +:fn-3x0: footnote:fn30[Commencing with release 3.0] :fnref-3x0: footnote:fn30:[] == Introduction @@ -43,7 +43,7 @@ Inline or external Javascript functions can be provided for any or all of the fo // tag::config-full[] NOTE: {sgw-s} 3.+ configuration of Javascript functions is done using the {rest-api-admin--xref}; specifically the {rest-api-admin--xref--access-control} and {rest-api-admin--xref--import-filter} endpoints. -Before 3.0 BETA, configuration was done within the database configuration -- see: <> +Before 3.0, configuration was done within the database configuration -- see: <> * Inline Javascript functions provided within the database configuration must be enclosed by a backtick pair (``). diff --git a/modules/ROOT/pages/_partials/common-releasenotes.adoc b/modules/ROOT/pages/_partials/common-releasenotes.adoc index 125df72d0..9010a03fa 100644 --- a/modules/ROOT/pages/_partials/common-releasenotes.adoc +++ b/modules/ROOT/pages/_partials/common-releasenotes.adoc @@ -61,7 +61,7 @@ Additional Detail:: * The ability to securely administer the Sync Gateway cluster using the admin REST endpoint enables programmatic control and simplifies remote administration in cloud deployments without relying on options like SSH-tunneling. * Maintaining a monolithic file is difficult especially if the configuration is complex. Multiple sync gateway databases may be defined in a single config file. This has potentially undesirable consequences in multi-tenant applications where database changes made for one tenant would require a restart of the node impacting all tenants. * A simple migration path ensures that existing JSON configurations are automatically converted to the new persistent modular configuration format on start-up. -Users can opt-out of this should they wish to continue working in legacy Pre-3.0 BETA configuration mode. +Users can opt-out of this should they wish to continue working in legacy Pre-3.0 configuration mode. // end::new-300-centralized-cfg-extended[] // tag::new-300-centralized-cfg[] diff --git a/modules/ROOT/pages/_partials/compatibility-cbl-sgw.adoc b/modules/ROOT/pages/_partials/compatibility-cbl-sgw.adoc index f21a9e8c3..4bdb0d837 100644 --- a/modules/ROOT/pages/_partials/compatibility-cbl-sgw.adoc +++ b/modules/ROOT/pages/_partials/compatibility-cbl-sgw.adoc @@ -36,7 +36,7 @@ The table below summarizes the compatible versions of Couchbase Lite with Sync G | 2.0 | 2.1 | 2.5 - 2.8 -| 3.0.0 (beta) +| 3.0.0 () | 1.4 *{fn-eos-sgw}* and 1.5 *{fn-eol-sgw}* | ✔ @@ -68,7 +68,7 @@ with delta sync enabled | ✔ | ✔ -| 3.0.0 (beta) +| 3.0.0 | ✖ | ✔ | ✔ diff --git a/modules/ROOT/pages/_partials/concepts/sync-function.adoc b/modules/ROOT/pages/_partials/concepts/sync-function.adoc index 4ff65a45a..0b40ceec0 100644 --- a/modules/ROOT/pages/_partials/concepts/sync-function.adoc +++ b/modules/ROOT/pages/_partials/concepts/sync-function.adoc @@ -112,7 +112,7 @@ If the document is being deleted, it will have a `_deleted` property with the v Your implementation of the sync function can omit the oldDoc parameter if you do not need it (JavaScript ignores extra parameters passed to a function). |Meta (optional) -|From 3.0 BETA the Sync Function includes support for a new `meta` argument. +|From 3.0 the Sync Function includes support for a new `meta` argument. This argument references the user defined XATTR that you are using to hold access grant data. diff --git a/modules/ROOT/pages/_partials/configuration/definitions/database_configuration_model.adoc b/modules/ROOT/pages/_partials/configuration/definitions/database_configuration_model.adoc index 247143923..6b76aff40 100644 --- a/modules/ROOT/pages/_partials/configuration/definitions/database_configuration_model.adoc +++ b/modules/ROOT/pages/_partials/configuration/definitions/database_configuration_model.adoc @@ -155,7 +155,7 @@ This property is intended to minimize accumulation of obsolete replication check The default is `7776000` seconds (90 days).|integer |**enable_shared_bucket_access** + -__optional__|*Deprecated at 3.0 BETA* +__optional__|*Deprecated at 3.0* use the `enable_shared_bucket_access` property to define whether to use extended attributes to store sync metadata; this is required to enable mobile-to-server data sync (_mobile convergence_). @@ -216,7 +216,7 @@ document.cookie = cookie1String; __optional__|This flag disallows cookies from being used by Javascript; by default javascript CAN use them + **Default** : `false`|boolean |**allow_conflicts** + -__optional__|**Deprecated at 3.0 * BETA* +__optional__|**Deprecated at 3.0 ** Use `allow_conflict` to define whether Sync Gateway will handle conflicts. diff --git a/modules/ROOT/pages/_partials/howto/how-to-assign-users-to-roles.adoc b/modules/ROOT/pages/_partials/howto/how-to-assign-users-to-roles.adoc index 8423fe9f4..84e320b8e 100644 --- a/modules/ROOT/pages/_partials/howto/how-to-assign-users-to-roles.adoc +++ b/modules/ROOT/pages/_partials/howto/how-to-assign-users-to-roles.adoc @@ -32,7 +32,7 @@ Admin REST API:: + -- -NOTE: The recommended method from 3.0 BETA +NOTE: The recommended method from 3.0 Assign a user to a role by sending a PUT request to the Admin REST API `_user` endpoint ({rest-api-admin-user-put--xref} ). diff --git a/modules/ROOT/pages/_partials/howto/how-to-control-document-access.adoc b/modules/ROOT/pages/_partials/howto/how-to-control-document-access.adoc index 53962ea9d..b37c8a079 100644 --- a/modules/ROOT/pages/_partials/howto/how-to-control-document-access.adoc +++ b/modules/ROOT/pages/_partials/howto/how-to-control-document-access.adoc @@ -25,9 +25,9 @@ You grant roles and-or users access to channels using: Using admin_channels property using the admin REST API endpoint -- see {rest-api-admin-user-put--xref} * Dynamically via Sync Function  +  Programmatically within the sync function using the exposed helper function access() — see {sync-function-api--xref} -* Configuration File (pre 3.0 BETA) + +* Configuration File (pre 3.0) + Using the appropriate `admin_channels` property in the {configuration-properties-legacy--xref}. + -*Note:* This option is disabled by default in 3.0 BETA; to use it, set the `disable_persistent_config` CLI or configuration file property flag to `true` and provide a full configuration +*Note:* This option is disabled by default in 3.0; to use it, set the `disable_persistent_config` CLI or configuration file property flag to `true` and provide a full configuration [#ex-read-access] .Allow Access @@ -66,7 +66,7 @@ In the case where channel assignment is done dynamically via the sync function, * The user/role can be derived or specified as a property within the document body. In this case, the document content itself is used to govern access and routing -* From 3.0 BETA, the role can be specified within a special user-defined XATTR associated with the document -- see: {access-control-how-use-xattrs-for-access-grants--xref}. +* From 3.0, the role can be specified within a special user-defined XATTR associated with the document -- see: {access-control-how-use-xattrs-for-access-grants--xref}. [{tabs}] @@ -186,7 +186,7 @@ It does so by requiring that the current user is the one recorded as an owner on Version 3.x:: + -- -This example makes use of channel data stored in XATTRS, an option introduced in 3.0 BETA -- see {access-control-how-use-xattrs-for-access-grants--xref} for more on this topic. +This example makes use of channel data stored in XATTRS, an option introduced in 3.0 -- see {access-control-how-use-xattrs-for-access-grants--xref} for more on this topic. [source, javascript] ---- diff --git a/modules/ROOT/pages/_partials/howto/how-to-create-roles.adoc b/modules/ROOT/pages/_partials/howto/how-to-create-roles.adoc index 72debf9f8..0c1ee8068 100644 --- a/modules/ROOT/pages/_partials/howto/how-to-create-roles.adoc +++ b/modules/ROOT/pages/_partials/howto/how-to-create-roles.adoc @@ -17,7 +17,7 @@ You can create and-or manage roles using the following options * Admin REST API: + Roles are created via the Sync Gateway Admin REST API -- see: {rest-api-admin--xref}. -* File-based Configuration Properties ( PRE 3.0 BETA) + +* File-based Configuration Properties ( PRE 3.0) + Configure roles in the xref:configuration-properties-legacy.adoc[Legacy Configuration Properties] file. + include::partial$block-caveats.adoc[tags=disable-persistent-config] diff --git a/modules/ROOT/pages/_partials/howto/how-to-create-users.adoc b/modules/ROOT/pages/_partials/howto/how-to-create-users.adoc index 7318ca87d..03117eb94 100644 --- a/modules/ROOT/pages/_partials/howto/how-to-create-users.adoc +++ b/modules/ROOT/pages/_partials/howto/how-to-create-users.adoc @@ -16,7 +16,7 @@ You create and-or manage users using the following options -- as shown in <> for the file contents. include::partial$block-caveats.adoc[tags=disable-persistent-config] diff --git a/modules/ROOT/pages/configuration-schema-database.adoc b/modules/ROOT/pages/configuration-schema-database.adoc index 4940f9dc1..4bfa217f5 100644 --- a/modules/ROOT/pages/configuration-schema-database.adoc +++ b/modules/ROOT/pages/configuration-schema-database.adoc @@ -20,7 +20,7 @@ include::partial$block-caveats.adoc[tags="legacy-config-equivalents"] == Introduction -From {sgw-te} 3.0 BETA you can use the Admin REST API to provision persistent configuration changes. +From {sgw-te} 3.0 you can use the Admin REST API to provision persistent configuration changes. This content introduces the <> and <> endpoints for convenience -- see {rest-api-admin--xref--database-configuration} for a full description of the endpoints available. diff --git a/modules/ROOT/pages/configuration-schema-db-security.adoc b/modules/ROOT/pages/configuration-schema-db-security.adoc index 40e03104d..5ec4cbf5d 100644 --- a/modules/ROOT/pages/configuration-schema-db-security.adoc +++ b/modules/ROOT/pages/configuration-schema-db-security.adoc @@ -21,7 +21,7 @@ include::partial$block-caveats.adoc[tags="legacy-config-equivalents"] == Introduction -In 3.0 BETA we use the Admin REST API `_user` and `_role` endpoints to provision and manage {sgw} users through persistent configuration changes. +In 3.0 we use the Admin REST API `_user` and `_role` endpoints to provision and manage {sgw} users through persistent configuration changes. This content introduces the <> and <> endpoints for convenience -- see {rest-api-admin--xref--database-security} for a full description of the endpoints available. diff --git a/modules/ROOT/pages/configuration-schema-isgr.adoc b/modules/ROOT/pages/configuration-schema-isgr.adoc index 65883c21a..4357d96c9 100644 --- a/modules/ROOT/pages/configuration-schema-isgr.adoc +++ b/modules/ROOT/pages/configuration-schema-isgr.adoc @@ -21,7 +21,7 @@ include::partial$block-caveats.adoc[tags="legacy-config-equivalents"] == Introduction -In 3.0 BETA we use the Admin REST API to provision persistent configuration changes. +In 3.0 we use the Admin REST API to provision persistent configuration changes. This content introduces the <> endpoint for convenience -- see {rest-api-admin--xref--replication} for a full description of the endpoints available. diff --git a/modules/ROOT/pages/get-started-install.adoc b/modules/ROOT/pages/get-started-install.adoc index 0bdcfa52e..a863b9d9d 100644 --- a/modules/ROOT/pages/get-started-install.adoc +++ b/modules/ROOT/pages/get-started-install.adoc @@ -63,12 +63,9 @@ NOTE: Ensure you have read -- and acted-upon -- the information in {get-started- include::partial$_get-started-topic-group.adoc[] -== Beta Release Only -{sgw-te} 3.0.0 (beta)01 is available for all xref:supported-environments.adoc[supported operating systems] as a direct download from here -- {downloads-mobile--xref}. +== Installation Process -Unpack the download to an appropriate location and install from there. -== Installation Process You can install Sync Gateway on any of the xref:supported-environments.adoc[supported operating systems]. On completion of this topic you should have a working Sync Gateway that you can extend and configure to meet your business needs. @@ -82,6 +79,7 @@ It is intended primarily to verify the success of the installation by proving a == Configuration + Sync Gateway's initial setup uses configuration details from a file its install script creates (`sync_gateway.json`, or `serviceconfig.json` on Windows). To provide your own configuration to Sync Gateway, you can either: diff --git a/modules/ROOT/pages/logging.adoc b/modules/ROOT/pages/logging.adoc index 00d89b69e..07c7970f1 100644 --- a/modules/ROOT/pages/logging.adoc +++ b/modules/ROOT/pages/logging.adoc @@ -35,7 +35,7 @@ include::partial$block-abstract.adoc[] :fn-clog: footnote:fn-clog[Introduced in Sync Gateway version 2.1] :fn-dep-cfg: footnote:fn-dep-cfg[The pre-2.1 logging configuration method, using 'logging.default` is deprecated. If upgrading from a pre2.1 Sync Gateway version, then will observer warnings on startup stating what is required to update your configuration -- see also: {legacy-logging-pre2-1--xref} ] -:fn-legacy-text: pass:q,a[For legacy Pre-3.0 BETA see xref:configuration-properties-legacy.adoc[legacy Pre-3.0 BETA configuration]] +:fn-legacy-text: pass:q,a[For legacy Pre-3.0 see xref:configuration-properties-legacy.adoc[legacy Pre-3.0 configuration]] :fn-legacy-pre-3-0: footnote:fnleg3-0[{fn-legacy-text}] :fnref-legacy-pre-3-0: footnote:fnleg3-0[] diff --git a/modules/ROOT/pages/secure-sgw-access.adoc b/modules/ROOT/pages/secure-sgw-access.adoc index 603162ccf..ad343662c 100644 --- a/modules/ROOT/pages/secure-sgw-access.adoc +++ b/modules/ROOT/pages/secure-sgw-access.adoc @@ -16,7 +16,7 @@ include::partial$block-abstract.adoc[] == Overview -From {sgw-te} 3.0 BETA, TLS is required by default for all communications with Couchbase Server. +From {sgw-te} 3.0, TLS is required by default for all communications with Couchbase Server. TLS v1.3 is supported as the default protocol. This approach means that that all endpoints communicating with {sgw} must also be encrypted, including: diff --git a/modules/ROOT/pages/upgrading.adoc b/modules/ROOT/pages/upgrading.adoc index fdce065e4..f540a1c5f 100644 --- a/modules/ROOT/pages/upgrading.adoc +++ b/modules/ROOT/pages/upgrading.adoc @@ -50,11 +50,11 @@ At a high level, a rolling upgrade consists of the following steps: Those steps are then repeated for each node in the {sgw} cluster. -== Upgrade to 3.0 BETA +== Upgrade to 3.0 === Using Persistent Configuration -The use of 3.0 BETA's Persistent Configuration feature is strongly recommended. +The use of 3.0's Persistent Configuration feature is strongly recommended. It is the default operational mode when starting {sgw}. The feature provides a smooth upgrade path for existing users by automatically converting their existing configuration files to the new persistent configuration format. @@ -62,7 +62,7 @@ The feature provides a smooth upgrade path for existing users by automatically c .One Way Upgrade [CAUTION] -- -The migration to 3.0 BETA configuration is a ONE WAY process; to continue using legacy-mode configuration see: <> +The migration to 3.0 configuration is a ONE WAY process; to continue using legacy-mode configuration see: <> -- Just startup a {sgw} node using your existing configuration properties file. @@ -105,7 +105,7 @@ Failing to do so may result in the configuration being overridden by one configu [#lbl-3-0-config-tls] === Secure Server Connection -Secure TLS Connection to Couchbase Server is enabled out-of-the-box in 3.0 BETA. +Secure TLS Connection to Couchbase Server is enabled out-of-the-box in 3.0. If you wish to use non-secure connection, perhaps in a test environment, you need to run {sgw} with {bootstrap-schema--xref--bootstrap-use-tls-server} set to `false` -- see: {secure-sgw-access--xref}