Closed dhoucgitter closed 1 year ago
May also be helpful to add a link to the DAC Postgres section.
May also be helpful to add a link to the DAC Postgres section.
@sayeun, there is a link to the DAC PostgreSQL CONFIG-VARS.md section here in the context of provisioning an external PostgreSQL cluster without using Viya4 IAC projects. Would you suggest adding a DAC PostgreSQL link along with the IAC PostgreSQL links, or elsewhere?
@sayeun, added "Post" prefix to document .md file name that was missed before.
@jkmin96, could you review and add comments for concerns or approve this PR if the updated doc content includes the requested changes that we discussed yesterday?
About title "## PostgreSQL Data Transfer Tool for the SAS Viya Platform - viya4-deployment Post-Transfer Steps (Experimental)" I'm still not sure it would be o.k. to use "Post-transfer" term for this doc.
About "### Using IAC to create an external PostgreSQL database server" Those PG instructions are based on the OOTB. Can user just run IAC to add the external PG w/o doing any extra work for Viya? As I mentioned yesterday, I thought that stopping Viya is a requirement before updating the existing cluster. Please make sure if stopping Viya is not necessary.
About title "## PostgreSQL Data Transfer Tool for the SAS Viya Platform - viya4-deployment Post-Transfer Steps (Experimental)" I'm still not sure it would be o.k. to use "Post-transfer" term for this doc.
About "### Using IAC to create an external PostgreSQL database server" Those PG instructions are based on the OOTB. Can user just run IAC to add the external PG w/o doing any extra work for Viya? As I mentioned yesterday, I thought that stopping Viya is a requirement before updating the existing cluster. Please make sure if stopping Viya is not necessary.
If the expected terraform plan/apply changes that are listed after only adding the PostgreSQL server map to their terraform-input.tfvars include destroying or re-creating a part of the cluster that Viya is currently using, for example substantive changes to existing resources other than the new PostgreSQL database server and recreating the jump server, then stopping Viya first makes sense. If the expected changes are just creating the PostgreSQL database server and jump server, I would not expect stopping Viya to be necessary. Since that advice can be left to some interpretation, perhaps we should always recommend stopping Viya, creating the new PostgreSQL server, then restarting Viya as the way to proceed. Thoughts?
Changes
default:
entry to reference an external database server by changing it tointernal: false
instead of completely removing the server map entry.