remove extra paragraph

sassoftware · Oct 27, 2023 · 352fe57 · 352fe57
1 parent 04d729d
commit 352fe57
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/docs/user/PostgreSQL.md b/docs/user/PostgreSQL.md
@@ -21,11 +21,8 @@ To use the IAC project to create an external PostgreSQL database cluster, refer
 
 ## Post Data Transfer Steps for viya4-deployment (Experimental)
 
-You had an existing SAS Viya platform deployment that was created using the viya4-deployment project and configured to use Crunchy as the database, and you have now completed the manual steps outlined in the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) to move your data over to an external PostgreSQL cluster. You now want to use the viya4-deployment project to manage your installation again.
-
 After you complete the steps outlined in the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) to move your data from an internal PostgreSQL server to an external PostgreSQL cluster, you can use the viya4-deployment project to manage your installation again. 
 
-
 ### Crunchy Data 5
 
 The final step in the [PostgreSQL Data Transfer Guide](https://documentation.sas.com/?cdcId=itopscdc&cdcVersion=default&docsetId=pgdatamig&docsetTarget=titlepage.htm) under "Post-transfer Steps for Crunchy Data 5" tells you to remove entries related to Crunchy Data and rebuild your manifests. Instead, you can remove the manual modifications you made to the `kustomization.yaml` and revise your `ansible-vars.yaml` so that the viya4-deployment project can manage your installation again.