Commit 6beca0a4 authored by Michael Leu's avatar Michael Leu 🌿
Browse files

docs: describe cloudsql.instanceId and cleanup formatting in cloudsql section

parent 0be05804
Pipeline #118013 passed with stages
in 17 minutes and 9 seconds
......@@ -18,6 +18,8 @@ env:
cloudsql:
enabled: true
# optional: override the instance name, defaults to $CUSTOMER_NAME-$APP_NAME-[review|dev|prod|stage]
instanceId: my-custom-instance-name
# post upgrade / intall jobs
# these get executed once after a deployment
......@@ -47,17 +49,16 @@ mailhog:
To use a Cloud SQL Postgresql database:
- set cloudsql.enabled: true in your values.yml as shown above
1. set cloudsql.enabled: true in your values.yml as shown above
create postgresql cloud sql instances for each environment
name: $CUSTOMER_NAME-$APP_NAME-[review|dev|prod|stage]
connectivity: public ip (no authorized networks needed)
note: pick the correct zone, machine type, backup location etc
warning: the name stays resevered even after the instance is deleted
use cloudsql.instanceId to override in case name is already taken
1. create postgresql cloud sql instances for each environment
name: $CUSTOMER_NAME-$APP_NAME-[review|dev|prod|stage]
connectivity: public ip (no authorized networks needed)
note: pick the correct zone, machine type, backup location etc
use catladder project-config-secrets [review|dev|prod|stage] to store
the postgresql password as POSTGRESQL_PASSWORD in app-secrets
warning: the name stays resevered even after the instance is deleted. Use `cloudsql.instanceId` to override in case name is already taken
1. use catladder project-config-secrets [review|dev|prod|stage] to store the postgresql password as POSTGRESQL_PASSWORD in app-secrets
## Resources
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment