(DOCSP-11234)(DOCSP-11122): updated feature control policy steps, oplog db auth, and blockstore db auth (#330)

* (DOCSP-11234)(DOCSP-11122): updated feature control policy steps, oplog db auth, and blockstore db auth

* (DOCSP-11234)(DOCSP-11122): fix highlighted lines

* (DOCSP-11234): copy review feedback

* (DOCSP-11234): feedback from filer

* (DOCSP-11234): minor tweaks

Author: jwilliams-mongo

source/includes/admonitions/fact-backing-db-auth.rst

@@ -1,3 +1,6 @@
+The Oplog database only supports the ``SCRAM`` authentication mechanism.
+You cannot enable other authentication mechanisms.
+
 If you enable ``SCRAM`` authentication on the oplog database, you
 must: 
 

source/includes/steps-deploy-k8s-opsmgr-http.yaml

@@ -212,7 +212,7 @@ content: |
     * - | ``spec``
         | ``.backup``
         | ``.opLogStores``
-        | ``.mongodbRef``
+        | ``.mongodbResourceRef``
         | ``.``:opsmgrkube:`~spec.backup.opLogStores.mongodbResourceRef.name`
       - string
       - Name of the MongoDB database resource for the oplog store.

source/includes/steps-deploy-k8s-opsmgr-https.yaml

@@ -271,7 +271,7 @@ content: |
      * - | ``spec``
          | ``.backup``
          | ``.opLogStores``
-         | ``.mongodbRef``
+         | ``.mongodbResourceRef``
          | ``.``:opsmgrkube:`~spec.backup.opLogStores.mongodbResourceRef.name`
        - string
        - Name of the MongoDB database resource for the oplog store.

source/reference/k8s-operator-om-specification.txt

@@ -352,7 +352,18 @@ Optional |onprem| Resource Settings
    blockstore. You must deploy this database resource in the same
    namespace as the |onprem| resource.
 
-   .. include:: /includes/admonitions/fact-backing-db-auth.rst
+   The blockstore database only supports the ``SCRAM`` authentication
+   mechanism. You cannot enable other authentication mechanisms.
+
+   If you enable ``SCRAM`` authentication on the blockstore database,
+   you must:
+
+   - Specify a MongoDB version earlier than v4.0 in the blockstore 
+     database resource definition.
+   - Create a MongoDB user resource to connect |onprem| to the
+     blockstore database.
+   - Specify the :opsmgrkube:`~spec.backup.blockStores.mongodbUserRef.name`
+     of the user in the |onprem| resource definition.
 
    .. include:: /includes/admonitions/watch-backup-resources.rst
 

source/reference/troubleshooting.txt

@@ -456,21 +456,30 @@ policy through the :opsmgr:`API </reference/api/controlled-features/update-contr
            --include \
            --request GET "https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0/groups/{PROJECT-ID}/controlledFeature?pretty=true"
 
-   .. important::
+   Save the response that the API returns. After you make changes in
+   the |onprem| application, you must add these policies back to
+   the project.
 
-      Save the response that the API returns. After you make changes in
-      the |onprem| application, you must add these policies back to
-      the project.
+   .. important:: 
+  
+      Note the highlighted fields and values in the following sample
+      response. You must send these same fields and values in later
+      steps when you remove and add feature control policies.
 
-   Your response should be similar to:
+      The ``externalManagementSystem.version`` field corresponds to the 
+      |k8s-op-short| version. You must send the exact same field value
+      in your requests later in this task.
 
+   Your response should be similar to:
+ 
    .. code-block:: json
+      :emphasize-lines: 3-7
 
       {
        "created": "2020-02-25T04:09:42Z",
        "externalManagementSystem": {
          "name": "mongodb-enterprise-operator",
-         "systemId": "6d6c139ae5528707b6e8e3b2",
+         "systemId": null,
          "version": "1.4.2"
        },
        "policies": [
@@ -484,12 +493,19 @@ policy through the :opsmgr:`API </reference/api/controlled-features/update-contr
          }
        ],
        "updated": "2020-02-25T04:10:12Z"
-     }
+      }
 
 #. :opsmgr:`Update </reference/api/controlled-features/update-controlled-features-for-one-project/>`
    the ``policies`` array with an empty list:
 
+   .. note::
+
+      The values you provide for the ``externalManagementSystem``
+      object, like the ``externalManagementSystem.version`` field, must
+      match values that you received in the response in Step 1.
+
    .. code-block:: sh
+      :emphasize-lines: 8-12
 
       curl --user "{USERNAME}:{APIKEY}" --digest \
            --header "Accept: application/json" \
@@ -500,7 +516,7 @@ policy through the :opsmgr:`API </reference/api/controlled-features/update-contr
              '{
                "externalManagementSystem": {
                  "name": "mongodb-enterprise-operator",
-                 "systemId": "6d6c139ae5528707b6e8e3b2",
+                 "systemId": null,
                  "version": "1.4.2"
                },
                "policies": []
@@ -514,7 +530,14 @@ policy through the :opsmgr:`API </reference/api/controlled-features/update-contr
 #. :opsmgr:`Update </reference/api/controlled-features/update-controlled-features-for-one-project/>`
    the ``policies`` array with the original feature control policies:
 
+   .. note::
+
+      The values you provide for the ``externalManagementSystem``
+      object, like the ``externalManagementSystem.version`` field, must
+      match values that you received in the response in Step 1.
+
    .. code-block:: sh
+      :emphasize-lines: 8-12
 
       curl --user "{USERNAME}:{APIKEY}" --digest \
            --header "Accept: application/json" \
@@ -525,7 +548,7 @@ policy through the :opsmgr:`API </reference/api/controlled-features/update-contr
              '{
                "externalManagementSystem": {
                  "name": "mongodb-enterprise-operator",
-                 "systemId": "6d6c139ae5528707b6e8e3b2",
+                 "systemId": null,
                  "version": "1.4.2"
                },
                "policies": [