(DOCSP-44174) Removes final nested components from OM (#453)

sarahsimpers · web-flow · commit f34ca15f2192 · 2024-10-07T14:43:47.000-04:00
- [DOCSP](https://jira.mongodb.org/browse/DOCSP-44174) **STAGING LINKS:** https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/admin/backup/restores-page https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/automation-config/automation-config-parameters https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/backup/get-snapshot-schedule https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/backup/update-one-snapshot-schedule-by-cluster-id https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/invitations/organizations/update-one-invitation https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/invitations/organizations/update-one-invitation-by-id https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/invitations/projects/update-one-invitation https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/invitations/projects/update-one-invitation-by-id https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/snapshots https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/snapshots/change-expiry-for-one-snapshot https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/third-party-integration-settings-create https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/api/third-party-integration-settings-update https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/reference/cluster-configuration https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/enable-ldap-authentication-for-group https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/enable-ssl-for-a-deployment https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/enable-x509-authentication-for-group https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/manage-mongodb-users https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/restore-replica-set https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/restore-sharded-cluster https://deploy-preview-453--10gen-docs-ops-manager.netlify.app/tutorial/third-party-service-integrations
diff --git a/source/includes/admonitions/important/change-pagerduty-integration-key.rst b/source/includes/admonitions/important/change-pagerduty-integration-key.rst
@@ -1,6 +1,4 @@
-.. important::
-
-   Changing the Integration Key doesn't change any alerts that use this
-   integration. Those alerts still use the previous Integration Key.
-
-   Remove and re-add each PagerDuty notification(s) to use the new key.
+:gold:`IMPORTANT:` Changing the Integration Key doesn't change any
+alerts that use this integration. Those alerts still use the previous
+Integration Key. Remove and re-add each PagerDuty notification to
+use the new key.
diff --git a/source/includes/api/automation-configuration/backupVersions.rst b/source/includes/api/automation-configuration/backupVersions.rst
@@ -53,12 +53,10 @@ settings, use the :ref:`update-backup-logs` endpoint.
      
        To learn more, see :doc:`/reference/mongodb-compatibility`.
 
-       .. important::
-
-          This property is read-only. Any modifications made to this
-          property are not reflected when updating the Backup Agent
-          through the |api|. To update the Backup Agent version, see
-          :ref:`this endpoint <update-monitoring-backup-versions>`.
+       :gold:`IMPORTANT:` This property is read-only. Any modifications
+       made to this property are not reflected when updating the Backup
+       Agent through the |api|. To update the Backup Agent version, see
+       :ref:`this endpoint <update-monitoring-backup-versions>`.
 
    * - backupVersions[n].hostname
      - string
diff --git a/source/includes/api/automation-configuration/monitoringVersions.rst b/source/includes/api/automation-configuration/monitoringVersions.rst
@@ -54,13 +54,11 @@ endpoint.
      
        To learn more, see :doc:`/reference/mongodb-compatibility`.
 
-       .. important::
-
-          This property is read-only. Any modifications made to this
-          property are not reflected when updating the Monitoring Agent
-          through the |api|.
-
-          To update the Monitoring Agent version, use :ref:`this endpoint <update-monitoring-backup-versions>`.
+       :gold:`IMPORTANT:` This property is read-only. Any modifications
+       made to this property are not reflected when updating the
+       Monitoring Agent through the |api|. To update the Monitoring
+       Agent version, see
+       :ref:`this endpoint <update-monitoring-backup-versions>`.
 
    * - monitoringVersions.hostname
      - string
diff --git a/source/includes/api/automation-configuration/sharding.rst b/source/includes/api/automation-configuration/sharding.rst
@@ -73,10 +73,9 @@ clusters.
      - Names of the config server hosts. The host names match the names
        used in each host's **processes.name** parameter.
 
-       If your sharded cluster runs MongoDB 3.4 or later, use
-       **sharding.configServerReplica**.
-
-       .. important:: MongoDB 3.4 removes support for mirrored config servers.
+       :gold:`IMPORTANT:` MongoDB 3.4 removes support for mirrored
+       config servers. If your sharded cluster runs MongoDB 3.4 or
+       later, use **sharding.configServerReplica**.
 
    * - sharding.shards
      - array of objects
diff --git a/source/includes/api/list-tables/snapshot-schedule/requests-opsmgr.rst b/source/includes/api/list-tables/snapshot-schedule/requests-opsmgr.rst
@@ -110,7 +110,5 @@
      - Number of weeks to retain weekly snapshots. You can set a value
        between ``1`` and ``52``, inclusive.
 
-       .. note::
-
-          Setting ``weeklySnapshotRetentionWeeks`` to ``0`` disables
-          this rule.
+       Setting ``weeklySnapshotRetentionWeeks`` to ``0`` disables
+       this rule.
diff --git a/source/includes/api/list-tables/snapshot-schedule/responses-opsmgr.rst b/source/includes/api/list-tables/snapshot-schedule/responses-opsmgr.rst
@@ -95,7 +95,5 @@
      - Number of weeks to retain weekly snapshots. |mms| may return
        values between ``1`` and ``52``, inclusive.
 
-       .. note::
-
-          Setting ``weeklySnapshotRetentionWeeks`` to ``0`` disables
-          this rule.
+       Setting ``weeklySnapshotRetentionWeeks`` to ``0`` disables
+       this rule.
diff --git a/source/includes/backup/select-restore-point.rst b/source/includes/backup/select-restore-point.rst
@@ -22,13 +22,11 @@
 
        .. include:: /includes/fact-restore-doesnt-include-selected-time.rst
 
-       .. important::
-
-          In FCV 4.0, you cannot perform a :abbr:`PIT (Point in Time)` restore
-          that covers any time prior to the latest backup resync. For the
-          conditions that cause a resync, see
-          :ref:`resync-backup`. This note does not apply to FCV 4.2
-          or later.
+       :gold:`IMPORTANT:` In FCV 4.0, you cannot perform a 
+       :abbr:`PIT(Point in Time)` restore that covers any time prior to
+       the latest backup resync. For the conditions that cause a
+       resync, see :ref:`resync-backup`. This note does not apply to
+       FCV 4.2 or later.
 
      - Select a :guilabel:`Date` and :guilabel:`Time`.
 
diff --git a/source/includes/extracts-api-third-party-integrations.yaml b/source/includes/extracts-api-third-party-integrations.yaml
@@ -30,15 +30,12 @@ content: |
                  .. include:: /includes/fact-api-key-redacted.rst
 
       * - Slack
-        - .. important::
-
-             Slack integrations now use the OAuth2 verification method
-             and must be initially configured, or updated from a legacy
-             integration, through the |service| :doc:`third-party
-             service integrations page
-             </tutorial/third-party-service-integrations>`.
-
-             Legacy tokens will soon no longer be supported.
+        - :gold:`IMPORTANT:` Slack integrations now use the OAuth2
+          verification method and must be initially configured, or
+          updated from a legacy integration, through the |service|
+          :doc:`third-party service integrations page
+          </tutorial/third-party-service-integrations>`. Legacy tokens
+          will soon no longer be supported.
 
           You must provide the following fields when you reconfigure an
           existing Slack integration:
@@ -269,15 +266,12 @@ content: |
                  .. include:: /includes/fact-api-key-redacted.rst
 
       * - Slack
-        - .. important::
-
-             Slack integrations now use the OAuth2 verification method
-             and must be initially configured, or updated from a legacy
-             integration, through the |service| :doc:`third-party
-             service integrations page
-             </tutorial/third-party-service-integrations>`.
-
-             Legacy tokens will soon no longer be supported.
+        - :gold:`IMPORTANT:` Slack integrations now use the OAuth2
+          verification method and must be initially configured, or
+          updated from a legacy integration, through the |service|
+          :doc:`third-party service integrations page
+          </tutorial/third-party-service-integrations>`. Legacy tokens
+          will soon no longer be supported.
 
           You must provide the following fields when you reconfigure an
           existing Slack integration:
diff --git a/source/includes/list-tables/admin-console/backup/restores.rst b/source/includes/list-tables/admin-console/backup/restores.rst
@@ -37,10 +37,9 @@
        - the number of times a Backup Daemon tried if the restore
          requires a Backup Daemon
 
-       .. important:: Legacy Value
-
-          No current restore delivery method retries a restore if it
-          fails. This column applies to obsolete restore methods.
+       :gold:`IMPORTANT:` No current restore delivery method retries a
+       restore if it fails. This column applies to obsolete restore
+       methods.
 
    * - Bytes Transferred
      - Total number of bytes that transferred while the restore job was
diff --git a/source/includes/list-tables/third-party-integration-settings-ui-cloud.rst b/source/includes/list-tables/third-party-integration-settings-ui-cloud.rst
@@ -56,12 +56,10 @@
        the integration will display your team name and |api| token, and
        allow you to change your channel name.
 
-       .. important:: Legacy Token Deprecation
-
-          Legacy tokens are deprecated and will be removed in a future
-          version of |mms|. You cannot edit a legacy token
-          integration. Instead, you must reconfigure your Slack
-          integration with OAuth2.
+       :gold:`IMPORTANT:` Legacy tokens are deprecated and will be
+       removed in a future version of |mms|. You cannot edit a legacy
+       token integration. Instead, you must reconfigure your Slack
+       integration with OAuth2.
 
    * - VictorOps Settings
 
diff --git a/source/includes/list-tables/third-party-integration-settings-ui.rst b/source/includes/list-tables/third-party-integration-settings-ui.rst
@@ -40,10 +40,8 @@
 
    * - Slack Settings
 
-       .. important::
-
-          Before proceeding, you must complete the steps to 
-          :ref:`integrate with Slack <integrate-with-slack>`.
+       :gold:`IMPORTANT:` Before proceeding, you must complete the
+       steps to :ref:`integrate with Slack <integrate-with-slack>`.
 
      - Team name, API token and a channel name for
        alert notifications sent to a Slack account. You can
@@ -61,12 +59,10 @@
        the integration will display your team name and |api| token, and
        allow you to change your channel name.
 
-       .. important:: Legacy Token Deprecation
-
-          Legacy tokens are deprecated and will be removed in a future
-          version of |mms|. You cannot edit a legacy token
-          integration. Instead, you must reconfigure your Slack
-          integration with OAuth2.
+       :gold:`IMPORTANT:` Legacy tokens are deprecated and will be
+       removed in a future version of |mms|. You cannot edit a legacy
+       token integration. Instead, you must reconfigure your Slack
+       integration with OAuth2.
 
    * - VictorOps Settings
 
@@ -123,10 +119,8 @@
            down, but Datadog reports them as healthy and the status 
            gets older.
 
-         .. important::
-
-            If the health status is ``1``, but no other metrics appear 
-            in Datadog, the replica set might be down.
+         :gold:`IMPORTANT:` If the health status is ``1`` but no other
+         metrics appear in Datadog, the replica set might be down.
 
    * - Webhook Settings
 
diff --git a/source/includes/steps-add-mongodb-user.yaml b/source/includes/steps-add-mongodb-user.yaml
@@ -51,11 +51,9 @@ content: |
 
        - Enter the user's password.
 
-         .. important::
-
-            If you specified ``$external`` as the database in the
-            :guilabel:`Identifier`, you do not need to specify a
-            password for the new user.
+         :gold:`IMPORTANT:` If you specified ``$external`` as the
+         database in the :guilabel:`Identifier`, you do not need to
+         specify a password for the new user.
 
      * - :guilabel:`Authentication Restrictions`
 
diff --git a/source/includes/steps-configure-existing-deployment-for-x509.yaml b/source/includes/steps-configure-existing-deployment-for-x509.yaml
@@ -43,9 +43,12 @@ content: |
           - Required
           - Provide the PEM key file password if you encrypted it.
 
-            .. important::
-
-               .. include:: /includes/fact-PKCS8-private-key.rst
+            :gold:`IMPORTANT:` If the encrypted private key for the 
+            ``.pem`` certificate file is in 
+            :wikipedia:`PKCS #8 </PKCS_8>` format, it must use
+            :rfc:`PBES2 <8018#section-6.2>` encryption operations. 
+            The {+mdbagent+} does not support PKCS #8 with other
+            encryption operations.
 
         * - :option:`tlsFIPSMode <mongod.--tlsFIPSMode>`
           - Optional
diff --git a/source/includes/steps-edit-mongodb-user.yaml b/source/includes/steps-edit-mongodb-user.yaml
@@ -40,11 +40,9 @@ content: |
 
        - Enter the user's password.
 
-         .. important::
-
-            If you specified ``$external`` as the database in the
-            :guilabel:`Identifier`, you do not need to change this 
-            value.
+         :gold:`IMPORTANT:` If you specified ``$external`` as the
+         database in the :guilabel:`Identifier`, you do not need to
+         change this value.
 
      * - :guilabel:`Authentication Restrictions`
 
diff --git a/source/includes/steps-restore-automatic-sharded-cluster.yaml b/source/includes/steps-restore-automatic-sharded-cluster.yaml
@@ -41,17 +41,13 @@ content: |
             objective for your snapshot. By default, the
             Oplog Store stores 24 hours of data.
 
-            .. example::
+            For example, if you select ``12:00``, the last operation in
+            the restore is ``11:59:59`` or earlier.
 
-               If you select ``12:00``, the last operation in the
-               restore is ``11:59:59`` or earlier.
-
-            .. important::
-
-               You can't perform a |pit| restore that covers any
-               time prior to the latest backup resync. For the
-               conditions that cause a resync, see
-               :doc:`/tutorial/resync-backup`.
+            :gold:`IMPORTANT:` You can't perform a |pit| restore that
+            covers any time prior to the latest backup resync. For the
+            conditions that cause a resync, see
+            :doc:`/tutorial/resync-backup`.
 
           - Select a :guilabel:`Date` and :guilabel:`Time`.
 
diff --git a/source/includes/steps-source-enable-authentication.yaml b/source/includes/steps-source-enable-authentication.yaml
@@ -170,11 +170,10 @@ content: |
 
           - Select either ``SASL`` or ``Simple``. 
 
-            .. important::
-
-               If you choose the ``Simple`` bind method, select ``TLS``
-               from the :guilabel:`Transport Security` because the
-               ``Simple`` bind method passes the password in plain text.
+            :gold:`IMPORTANT:` If you choose the ``Simple`` bind
+            method, select ``TLS`` from the 
+            :guilabel:`Transport Security` because the
+            ``Simple`` bind method passes the password in plain text.
 
         * - SASL Mechanisms  
 
diff --git a/source/reference/api/invitations/organizations/update-one-invitation-by-id.txt b/source/reference/api/invitations/organizations/update-one-invitation-by-id.txt
@@ -85,13 +85,10 @@ Request Body Parameters
        If the user accepts the invitation, |mms| assigns these roles
        to them.
 
-       .. important::
-
-          |mms| replaces the **roles** in the invitation with
-          those that you provide in this request.
-
-          Ensure that you include all roles that you want to assign the
-          user in this request.
+       :gold:`IMPORTANT:` |mms| replaces the **roles** in the
+       invitation with the roles that you provide in this request.
+       Ensure that you include all roles that you want to assign the
+       user in this request.
 
 Response
 --------
diff --git a/source/reference/api/invitations/organizations/update-one-invitation.txt b/source/reference/api/invitations/organizations/update-one-invitation.txt
@@ -76,13 +76,10 @@ Request Body Parameters
        If the user accepts the invitation, |mms| assigns these roles
        to them.
 
-       .. important::
-
-          |mms| replaces the **roles** in the invitation with
-          those that you provide in this request.
-
-          Ensure that you include all roles that you want to assign the
-          user in this request.
+       :gold:`IMPORTANT:` |mms| replaces the **roles** in the
+       invitation with the roles that you provide in this request.
+       Ensure that you include all roles that you want to assign the
+       user in this request.
 
    * - username
      - string
diff --git a/source/reference/api/invitations/projects/update-one-invitation-by-id.txt b/source/reference/api/invitations/projects/update-one-invitation-by-id.txt
@@ -86,13 +86,10 @@ Request Body Parameters
        If the user accepts the invitation, |mms| assigns these
        roles to them.
 
-       .. important::
-
-          |mms| replaces the **roles** in the invitation with
-          those that you provide in this request.
-
-          Ensure that you include all roles that you want to assign the
-          user in this request.
+       :gold:`IMPORTANT:` |mms| replaces the **roles** in the
+       invitation with the roles that you provide in this request.
+       Ensure that you include all roles that you want to assign the
+       user in this request.
 
 Response
 --------
diff --git a/source/reference/api/invitations/projects/update-one-invitation.txt b/source/reference/api/invitations/projects/update-one-invitation.txt
@@ -76,13 +76,10 @@ Request Body Parameters
        If the user accepts the invitation, |mms| assigns these
        roles to them.
 
-       .. important::
-
-          |mms| replaces the **roles** in the invitation with
-          those that you provide in this request.
-
-          Ensure that you include all roles that you want to assign the
-          user in this request.
+       :gold:`IMPORTANT:` |mms| replaces the **roles** in the
+       invitation with the roles that you provide in this request.
+       Ensure that you include all roles that you want to assign the
+       user in this request.
 
    * - username
      - string
diff --git a/source/reference/api/snapshots.txt b/source/reference/api/snapshots.txt
@@ -49,11 +49,9 @@ The following lists the endpoints available for snapshots.
      - :doc:`/groups/{groupId}/clusters/{clusterId}/snapshots/{snapshotId} </reference/api/snapshots/remove-one-snapshot-from-one-cluster>`
      - Remove one snapshot.
 
-       .. important::
-
-          To delete a snapshot, you must issue the request from an IP
-          address on your user account's
-          :ref:`access list <access-list-for-api-operations>`.
+       :gold:`IMPORTANT:` To delete a snapshot, you must issue the
+       request from an IP address on your user account's
+       :ref:`access list <access-list-for-api-operations>`.
 
 .. important:: Deprecated when using MongoDB 3.4
 
diff --git a/source/reference/api/snapshots/change-expiry-for-one-snapshot.txt b/source/reference/api/snapshots/change-expiry-for-one-snapshot.txt
