(DOCSP-20142) Separate out procedure into YAML steps file (#976)

* (DOCSP-20142) Recreating branch after conflict

* (DOCSP-20142) Reference steps document.

Author: lmkerbey-mdb

source/includes/steps-create-operator-credentials.yaml

@@ -0,0 +1,56 @@
+---
+stepnum: 1
+ref: create-operator-credentials-create
+title: Create a new Kubernetes secret
+content: |
+
+  a. Ensure you have the Public and Private Keys for your desired
+     |onprem| |svc-api-key|.
+
+  b. Invoke the following |k8s| command to create your secret:
+
+     .. code-block:: sh
+
+        kubectl -n <metadata.namespace> \
+        create secret generic <mycredentials> \
+        --from-literal="publicKey=<publicKey>" \
+        --from-literal="privateKey=<privateKey>"
+
+     The ``-n`` flag limits the |k8s-ns| to which this secret applies.
+     All MongoDB |k8s| resources must exist in the same namespace as the
+     |k8s-secrets| and |k8s-configmaps|. The |k8s-op-short| doesn't use
+     either the secrets or ConfigMaps.
+
+     .. note::
+
+        The deprecated version of this command specifies a ``user`` and ``publicApiKey``
+        instead of a ``publicKey`` and ``privateKey``. |k8s-op-short| accepts
+        either version for authentication.
+
+---
+stepnum: 2
+ref: create-operator-credentials-verify
+title: Verify your new Kubernetes secret
+content: |
+
+  Invoke the following |k8s| command to verify your secret:
+
+  .. code-block:: sh
+
+     kubectl describe secrets/<mycredentials> -n <metadata.namespace>
+
+  This command returns a secret description in the shell:
+
+  .. code-block:: sh
+
+     Name:         <mycredentials>
+     Namespace:    <metadata.namespace>
+     Labels:       <none>
+     Annotations:  <none>
+
+     Type:  Opaque
+
+     Data
+     ====
+     privateKey:  31 bytes
+     publicKey:          22 bytes

source/tutorial/create-operator-credentials.txt

@@ -56,48 +56,4 @@ Procedure
 
 To create your |k8s| secret:
 
-1. Make sure you have the Public and Private Keys for your desired
-   |onprem| |svc-api-key|.
-
-2. Invoke the following |k8s| command to create your secret:
-
-   .. code-block:: sh
-
-      kubectl -n <metadata.namespace> \
-        create secret generic <mycredentials> \
-        --from-literal="publicKey=<publicKey>" \
-        --from-literal="privateKey=<privateKey>"
-
-   The ``-n`` flag limits the |k8s-ns| to which this secret applies.
-   All MongoDB |k8s| resources must exist in the same namespace as the
-   |k8s-secrets| and |k8s-configmaps|. The |k8s-op-short| doesn't use
-   either the secrets or ConfigMaps.
-
-   .. note::
-
-      The deprecated version of this command specifies a ``user`` and ``publicApiKey``
-      instead of a ``publicKey`` and ``privateKey``. |k8s-op-short| accepts
-      either version for authentication.
-
-3. Invoke the following |k8s| command to verify your secret:
-
-   .. code-block:: sh
-
-      kubectl describe secrets/<mycredentials> -n <metadata.namespace>
-
-   This command returns a secret description in the shell:
-
-   .. code-block:: sh
-
-      Name:         <mycredentials>
-      Namespace:    <metadata.namespace>
-      Labels:       <none>
-      Annotations:  <none>
-
-      Type:  Opaque
-
-      Data
-      ====
-      privateKey:  31 bytes
-      publicKey:          22 bytes
-
+.. include:: /includes/steps/create-operator-credentials.rst