(DOCSP-37380) Updates all remaining config file pages to template (#358)

* (DOCSP-37380) Updates all remaining config file pages to template

* Adds second action template

* Tests replacements on cluster page

* Updates clusters page

* Changes OA, alert pages

* Fixes error

* Fix template issue

Author: sarahsimpers

source/includes/steps-config-file-template-action-2.rst

@@ -0,0 +1,24 @@
+Follow these steps to |action 2| with a configuration file:
+
+.. procedure::
+   :style: normal
+
+   .. step:: Copy the sample request for |openapi-link 2|.
+
+      a. Navigate to the |openapi-link 2|
+         section of the |service| Admin API specification.
+      b. Under :guilabel:`Request samples` on the right side, click
+         :guilabel:`Expand all`.
+      c. Click :guilabel:`Copy` to copy the sample request.
+
+   .. step:: Create the configuration file.
+    
+      a. Paste the sample request into a text editor and change
+         the values to reflect your desired configuration.
+      b. Save the file with a ``.json`` extension.
+
+   .. step:: Run the |atlas-cli command 2| command with 
+      the ``--file`` option.
+
+      Specify the path to the file you saved with the ``--file`` flag.
+

source/includes/steps-config-file-template-action-3.rst

@@ -0,0 +1,24 @@
+Follow these steps to |action 3| with a configuration file:
+
+.. procedure::
+   :style: normal
+
+   .. step:: Copy the sample request for |openapi-link 3|.
+
+      a. Navigate to the |openapi-link 3|
+         section of the |service| Admin API specification.
+      b. Under :guilabel:`Request samples` on the right side, click
+         :guilabel:`Expand all`.
+      c. Click :guilabel:`Copy` to copy the sample request.
+
+   .. step:: Create the configuration file.
+    
+      a. Paste the sample request into a text editor and change
+         the values to reflect your desired configuration.
+      b. Save the file with a ``.json`` extension.
+
+   .. step:: Run the |atlas-cli command 3| command with 
+      the ``--file`` option.
+
+      Specify the path to the file you saved with the ``--file`` flag.
+

source/reference/json/alert-config-file.txt

@@ -10,104 +10,49 @@ Alert Configuration File
    :depth: 1
    :class: singlecol
 
-You can use a configuration file to specify the
-settings for :ref:`creating <atlas-alerts-settings-create>`
-or :ref:`updating <atlas-alerts-settings-update>` an alert
-configuration through the {+atlas-cli+}. The {+atlas-cli+}
-accepts ``.json`` configuration files.
 
-.. _alert-config-settings:
-
-Alert Configuration Settings
-----------------------------
-
-Depending on the type of alert configuration, you can specify the 
-following settings to create or update an alert configuration 
-in a configuration file:
-
-.. list-table::
-   :widths: 20 10 70
-   :header-rows: 1
+.. This page differs from the main template because it documents
+.. multiple commands For a one-command
+.. template, use the template on cloud-backup-schedule-config-file.txt
 
-   * - Field
-     - Type
-     - Description
+.. |atlas-cli command| replace:: :ref:`atlas-alerts-settings-create`
+.. |configuration-file-name| replace:: alert configuration  
+.. |openapi-link| replace:: :oas-atlas-op:`Create One Alert Configuration in One Project </Alert-Configurations/operation/createAlertConfiguration>`
+.. |action| replace:: create an alert configuration
 
-   * - ``enabled``
-     - boolean
-     - Flag that indicates whether someone enabled this
-       alert configuration for the specified project.
+.. |atlas-cli command 2| replace:: :ref:`atlas-alerts-settings-update`
+.. |openapi-link 2| replace:: :oas-atlas-tag:`Update One Alert Configuration for One Project </Alert-Configurations/operation/updateAlertConfiguration>`
+.. |action 2| replace:: update an alert configuration
 
-   * - ``eventTypeName``
-     - string
-     - Required. Event type that triggers an alert.
+You can use a |configuration-file-name| file to specify the
+settings required when you |action| or |action 2|
+using the {+atlas-cli+}. The {+atlas-cli+} accepts ``.json`` 
+|configuration-file-name| files.
 
-   * - ``matchers``
-     - array of objects
-     - Rules to apply when matching an object against this alert
-       configuration. You can use this field only if the ``eventTypeName``
-       specifies an event for a host, replica set, or sharded cluster.
-
-   * - ``metricThreshold``
-     - object
-     - Threshold for the metric that, when exceeded, triggers an alert.
-       You can use this field only if the ``eventTypeName`` reflects
-       a change in measurement or metric.
-
-   * - ``notifications``
-     - array of objects
-     - List that contains the targets that |service| sends notifications.
+.. _alert-config-settings:
 
-   * - ``threshold``
-     - object
-     - A limit that triggers an alert when exceeded.
+Available Settings
+------------------
 
-For detailed descriptions and a full list of available settings,
-see the request body schema in the API specification:
+When you |action| using a configuration file, you
+can specify any settings that are listed in 
+|openapi-link| under :guilabel:`Request Body Schema`.
 
-- :oas-atlas-op:`Create One Alert Configuration in One Project </createAlertConfiguration>`
-- :oas-atlas-op:`Update One Alert Configuration for One Project </updateAlertConfiguration>`
+When you |action 2| using a configuration file, you
+can specify any settings that are listed in 
+|openapi-link 2| under :guilabel:`Request Body Schema`.
 
 .. _example-alert-config-file:
 
-Example Alert Configuration File
---------------------------------
-
-To create or update an alert configuration, specify the
-fields that you want to include in the configuration file.
-For example, the following sample file enables an alert 
-configuration that notifies you when a replica set called 
-``event-replica-set`` loses its primary node:
-
-.. literalinclude:: /includes/alert-configuration-config-file.json
-
-Example Alert Configuration Commands
-------------------------------------
-
-After you create the file, run the {+atlas-cli+} 
-command to create or update the alert configuration.
+Create a Configuration File
+---------------------------
 
 Create an Alert Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To create an alert configuration, specify the ``--flag`` option 
-and the path to the file. The following example creates an 
-alert configuration by using a configuration file named 
-``alert-config.json``:
-
-.. code-block::
-
-   atlas alerts settings create --file /alert-config.json
+.. include:: /includes/steps-config-file-template.rst
 
 Update an Alert Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To update an alert configuration, specify the ID of the
-alert configuration that you want to update, the ``--flag``
-option, and the path to the file. The following example updates 
-an existing alert configuration by using a configuration file 
-named ``alert-config.json``:
-
-.. code-block::
-
-   atlas alerts settings update <alertConfigId> --file /alert-config.json
+.. include:: /includes/steps-config-file-template-action-2.rst