consolidate steps

sassoftware · Oct 24, 2023 · 323cca2 · 323cca2
1 parent 5066e4d
commit 323cca2
Showing 1 changed file with 5 additions and 6 deletions.
diff --git a/docs/user/PostPostgreSQLDataTransfer_Experimental.md b/docs/user/PostPostgreSQLDataTransfer_Experimental.md
@@ -36,9 +36,8 @@ You had an existing SAS Viya platform deployment that was created using the viya
 
 #### Crunchy 4 
 
-1. While following the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" in Step 5 you are asked to remove all entries in your kustomization.yaml that contain a set of strings that are used for Crunchy 4 Data PostgreSQL configuration.
-2. Since the viya4-deployment project automatically manages the configuration and creation of the PostgreSQL related entries in your kustomziation.yaml, you can skip Step 5 from the "Steps for Crunchy Data 4" for now.
-3. You will now need to configure your ansible-vars.yaml to make the switch over from Crunchy Data PostgreSQL to an external PostgreSQL cluster.
+1. While following the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" in Step 5 you are asked to remove all entries in your kustomization.yaml that contain a set of strings that are used for Crunchy 4 Data PostgreSQL configuration. Since the viya4-deployment project automatically manages the configuration and creation of the PostgreSQL related entries in your kustomziation.yaml, you can skip Step 5 from the "Steps for Crunchy Data 4" for now.
+2. You will now need to configure your ansible-vars.yaml to make the switch over from Crunchy Data PostgreSQL to an external PostgreSQL cluster.
       * If as part of your data transfer, you provisioned your PostgreSQL clusters using any [Viya 4 IAC projects](https://github.com/search?q=org%3Asassoftware+viya4-iac-&type=repositories), then your PostgreSQL configuration and connection information should already be present in the .tfstate file, so you don't need to add those entries in your `ansible-vars.yaml`. You should modify the `V4_CFG_POSTGRES_SERVERS` variable if it's still configured to use an internal Crunchy instance like so:
       ```yaml
       # modify as below to use external instance
@@ -47,6 +46,6 @@ You had an existing SAS Viya platform deployment that was created using the viya
           internal: false
       ```
       * If as part of your data transfer, you provisioned your PostgreSQL clusters without the use of a Viya 4 IAC project, then you will need to manually add definitions for each of your PostgreSQL clusters. You can see an example definition here in our [CONFIG-VARS.md documentation](https://github.com/sassoftware/viya4-deployment/blob/main/docs/CONFIG-VARS.md#postgresql)
-4. Going back to the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" perform Step 8 and start the operator if your deployment is managed by the SAS Deployment Operator (if `V4_DEPLOYMENT_OPERATOR_ENABLED` was set to true)
-5. Run the ansible-playbook again with the `viya,install` tags. This will update the kustomization.yaml by removing entries related to Crunchy 4 and add entries for your external PostgreSQL cluster, all managed by viya4-deployment. The manifest will be rebuilt and reapplied to the cluster.
-6. Go back to the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" and perform Steps 10 and onwards to complete the data transfer.
+3. Going back to the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" perform Step 8 and start the operator if your deployment is managed by the SAS Deployment Operator (if `V4_DEPLOYMENT_OPERATOR_ENABLED` was set to true)
+4. Run the ansible-playbook again with the `viya,install` tags. This will update the kustomization.yaml by removing entries related to Crunchy 4 and add entries for your external PostgreSQL cluster, all managed by viya4-deployment. The manifest will be rebuilt and reapplied to the cluster.
+5. Go back to the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Steps for Crunchy Data 4" and perform Steps 10 and onwards to complete the data transfer.