(DOCSP-36854): Backport DOCSP-36633 to v7.0. (#95)

corryroot · corryroot · commit 7392d922735b · 2024-02-15T11:05:57.000-05:00
@TomerYakir, I tried to clarify the wording around the MDB Settings. The ticket suggests removing the list of unsupported settings. Should we really do that? [STAGE](https://preview-mongodbcorryroot.gatsbyjs.io/ops-manager/DOCSP-36633/reference/cluster-configuration-process-options/) [JIRA](https://jira.mongodb.org/browse/DOCSP-36633) [BUILD](https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=65ce2e717111165982e64f8d)
diff --git a/source/includes/api/automation-configuration/processes.rst b/source/includes/api/automation-configuration/processes.rst
@@ -67,9 +67,11 @@ instances. Using this array, you can:
      - Required
      - MongoDB configuration object for MongoDB versions 2.6 and later.
 
-       .. seealso::
+       .. note::
 
-          :doc:`Supported configuration options </reference/cluster-configuration-process-options>`.
+          The ``processes.args2_6`` object accepts most MongoDB 
+          settings and parameters for MongoDB versions 2.6 and later. 
+          To learn more, see :ref:`om-unsupported-mdb-settings`.
 
    * - processes[n].alias
      - string
diff --git a/source/includes/api/list-tables/controlled-features-request.rst b/source/includes/api/list-tables/controlled-features-request.rst
@@ -88,6 +88,6 @@
        | ``.disabledParams``
      - array
      - List of |mongod| settings to disable when you apply the
-       ``DISABLE_SET_MONGOD_CONFIG`` policy. For information about
-       accepted values, see :doc:`Supported MongoDB Options for
-       Automation </reference/cluster-configuration-process-options>`.
+       ``DISABLE_SET_MONGOD_CONFIG`` policy. Automation doesn't support 
+       all MongoDB options, which can result in failed import attempts. 
+       To learn more, see :ref:`om-unsupported-mdb-settings`.
diff --git a/source/includes/api/list-tables/controlled-features-response.rst b/source/includes/api/list-tables/controlled-features-response.rst
@@ -101,6 +101,6 @@
        | ``.disabledParams``
      - array
      - List of |mongod| settings to disable if you apply the
-       ``DISABLE_SET_MONGOD_CONFIG`` policy. For information about
-       possible values, see :doc:`Supported MongoDB Options for
-       Automation </reference/cluster-configuration-process-options>`.
+       ``DISABLE_SET_MONGOD_CONFIG`` policy. Automation doesn't support 
+       all MongoDB options, which can result in failed import attempts. 
+       To learn more, see :ref:`om-unsupported-mdb-settings`.
diff --git a/source/includes/steps-create-cluster-through-api.yaml b/source/includes/steps-create-cluster-through-api.yaml
@@ -82,8 +82,9 @@ content: |
   cluster.
 
   Specify the ``args2_6`` syntax for the ``processes.<args>`` field.
-  See :doc:`/reference/cluster-configuration-process-options` for more
-  information.
+  The ``processes.args2_6`` object accepts most MongoDB settings and 
+  parameters for MongoDB versions 2.6 and later. To learn more, see 
+  :ref:`om-unsupported-mdb-settings`.
 
   .. code-block:: javascript
      :linenos:
diff --git a/source/includes/toc-reference.yaml b/source/includes/toc-reference.yaml
@@ -44,8 +44,8 @@ edition:
 ---
 file: /reference/cluster-configuration-process-options
 description: |
-  Supported options for a MongoDB process as specified in the automation
-  configuration file.
+  Supported and unsupported options for a MongoDB process as specified 
+  in the automation configuration file.
 ---
 file: /reference/required-permissions-aws-user
 description: |
diff --git a/source/reference.txt b/source/reference.txt
@@ -31,8 +31,8 @@ Reference
   determine the desired state of the MongoDB deployment.
 
 :doc:`/reference/cluster-configuration-process-options`
-  Supported options for a MongoDB process as specified in the automation
-  configuration file.
+  Supported and unsupported options for a MongoDB process as specified 
+  in the automation configuration file.
 
 :doc:`/reference/monitoring`
   A reference sheet for the monitoring service.
diff --git a/source/reference/cluster-configuration-process-options.txt b/source/reference/cluster-configuration-process-options.txt
@@ -1,6 +1,8 @@
-=========================================
-MongoDB Settings that Automation Supports
-=========================================
+.. _om-unsupported-mdb-settings:
+
+=======================================
+MongoDB Settings and Automation Support
+=======================================
 
 .. default-domain:: mongodb
 
@@ -22,18 +24,12 @@ Unsupported Settings
 
 This object doesn't support the following settings:
 
-- :setting:`net.tls.allowInvalidCertificates`
-- :setting:`net.tls.allowInvalidHostnames`
+.. important::
+
+   Specific security-related settings, such as LDAP settings, TLS 
+   settings related to the Certificate Authority, and Authentication 
+   settings, are managed at the project level and may be overridden 
+   upon import into Automation.
+
 - :configexpansion:`__exec`
 - :configexpansion:`__rest`
-- :setting:`security.ldap.servers`
-- :setting:`security.ldap.bind.queryUser`
-- :setting:`security.ldap.bind.queryPassword`
-- :setting:`security.ldap.bind.useOSDefaults`
-- :setting:`security.ldap.bind.method`
-- :setting:`security.ldap.bind.saslMechanisms`
-- :setting:`security.ldap.transportSecurity`
-- :setting:`security.ldap.timeoutMS`
-- :setting:`security.ldap.userToDNMapping`
-- :setting:`security.ldap.authz.queryTemplate`
-- :setting:`security.ldap.validateLDAPServerConfig`
diff --git a/source/tutorial/add-existing-mongodb-processes.txt b/source/tutorial/add-existing-mongodb-processes.txt
@@ -37,8 +37,9 @@ Deployments must have unique names within the projects.
 MongoDB Configuration Options
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Automation doesn't support all MongoDB options. To review which options
-are supported, see :doc:`/reference/cluster-configuration-process-options`.
+Automation doesn't support all MongoDB options, which can result in 
+failed import attempts. To learn more, see 
+:ref:`om-unsupported-mdb-settings`.
 
 |tls|
 ~~~~~
diff --git a/source/tutorial/add-monitored-deployment-to-automation.txt b/source/tutorial/add-monitored-deployment-to-automation.txt
@@ -27,9 +27,9 @@ and deploy changes as needed.
 Considerations
 --------------
 
-Automation supports most but not all available MongoDB options. See
-:doc:`/reference/cluster-configuration-process-options` for unsupported
-MongoDB deployment options.
+Automation doesn't support all MongoDB options, which can result in 
+failed import attempts. To learn more, see 
+:ref:`om-unsupported-mdb-settings`.
 
 When adding a MongoDB deployment requiring authentication, you have the
 option of importing that process's users and roles. During import,
diff --git a/source/tutorial/update-mongodb-version-of-deployment-via-api.txt b/source/tutorial/update-mongodb-version-of-deployment-via-api.txt
@@ -21,8 +21,9 @@ as would be the case if you used the tutorial to
 Consideration
 -------------
 
-The |api| supports the MongoDB options listed on the
-:doc:`/reference/cluster-configuration-process-options` page.
+The |api| supports most MongoDB settings and parameters for MongoDB 
+versions 2.6 and later. To learn more, see 
+:ref:`om-unsupported-mdb-settings`.
 
 .. _api-tutorial-update-mongodb-version-variables:
 
