|
| 1 | +# ADMIN DATABASE CONNECTION INFO |
| 2 | +# Postgres used for catalog, visibility and temporal history. |
| 3 | +PG_HOST= # not required if using in-cluster postgres |
| 4 | +PG_PORT=5432 |
| 5 | +PG_USER=postgres |
| 6 | +PG_PASSWORD= # not required if using in-cluster postgres |
| 7 | +PG_DATABASE=postgres |
| 8 | +PG_RDS_SSL_ENABLED=false # If using RDS catalog specifically, it will auto-pick up the certificate required for SSL |
| 9 | + |
| 10 | +# TEMPORAL DATABASE SETTINGS |
| 11 | +# The following variables dictate the name of the user and databases that will |
| 12 | +# be created in Postgres to be used by Temporal. These are all required. Edit |
| 13 | +# these to your liking. |
| 14 | + |
| 15 | +# These are irrelevant for Temporal Cloud. |
| 16 | +TEMPORAL_USER=temporal-pg-user |
| 17 | +TEMPORAL_PASSWORD=temporal-pg-password # not required if using in-cluster postgres |
| 18 | + |
| 19 | +# DO NOT CHANGE THESE. |
| 20 | +# These are used by temporal and currently hardcoded for Postgres. |
| 21 | +TEMPORAL_DB=temporal |
| 22 | +TEMPORAL_VISIBILITY_DB=temporal_visibility |
| 23 | + |
| 24 | +TEMPORAL_SSL_MODE=false # Should be false if using in-cluster catalog, set true for RDS etc. |
| 25 | +# TEMPORAL_SSL_CA_CERT_PATH=./aws-ca-bundle.pem |
| 26 | + |
| 27 | + |
| 28 | +# PEERDB SETTINGS |
| 29 | +# env variables for peerdb deployment |
| 30 | +PEERDB_VERSION=stable-v0.12.2 |
| 31 | +# name of the database that will be used by peerdb. |
| 32 | +PEERDB_CATALOG_DATABASE=peerdb_catalog_db |
| 33 | +PEERDB_CATALOG_CREDS_SECRET_NAME=catalog-db-manual-creds |
| 34 | +PEERDB_RELEASE_NAME=peerdb-rel |
| 35 | +PEERDB_K8S_NAMESPACE=peerdb-ns |
| 36 | +PEERDB_PASSWORD=peerdb |
| 37 | +PEERDB_UI_PASSWORD=peerdb |
| 38 | +PEERDB_UI_NEXTAUTH_SECRET=R5f6vc1@6@@VZABJ8t0gYhhKLgAAchrTLaRrkVRY # !! CHANGE THIS TO A NEW RANDOMLY GENERATED STRING !! |
| 39 | +PEERDB_UI_SERVICE_URL= #Add the external IP/DNS from where PeerDB UI is being accessed. eg. http://aws.loadbalancer.cname:3000 |
| 40 | +SERVICE_ACCOUNT_NAME=peerdb-sa |
| 41 | + |
| 42 | + |
| 43 | +# TEMPORAL SETTINGS |
| 44 | +# For Self-Hosted Temporal, the namespace is 'default'. |
| 45 | +# For Temporal Cloud, set it to your Temporal Namespace name. This will be of the form nmspc.abc12 |
| 46 | +PEERDB_TEMPORAL_NAMESPACE=default |
| 47 | + |
| 48 | +# The below 3 variables are for Temporal Cloud ONLY. |
| 49 | +# TEMPORAL_CLOUD_HOST will be of the form <namespace_name>.tmprl.cloud (port is 7233, omit it here) |
| 50 | +TEMPORAL_CLOUD_HOST= |
| 51 | +# TEMPORAL_CLIENT_CERT and TEMPORAL_CLIENT_KEY are derived from the ROOT CA used in namespace creation |
| 52 | +# These must be BASE64 strings |
| 53 | +TEMPORAL_CLOUD_CLIENT_CERT= |
| 54 | +TEMPORAL_CLOUD_CLIENT_KEY= |
| 55 | +# This can be any string. It is used to identify the deployment in Temporal Cloud. |
| 56 | +PEERDB_DEPLOYMENT_UID= |
| 57 | + |
| 58 | +# AWS SETTINGS |
| 59 | +AWS_REGION= |
| 60 | + |
| 61 | +# Option 1: Use AWS Credentials explicitly |
| 62 | +AWS_ACCESS_KEY_ID= |
| 63 | +AWS_SECRET_ACCESS_KEY= |
| 64 | + |
| 65 | +# Option 2: Use AWS IAM role via service account |
| 66 | +AWS_ROLE_ARN= |
| 67 | + |
| 68 | + |
| 69 | + |
| 70 | +# For setting up authentication |
| 71 | +AUTHENTICATION_ENABLED=false |
| 72 | +AUTHENTICATION_CREDENTIALS_USERNAME= |
| 73 | +AUTHENTICATION_CREDENTIALS_PASSWORD= |
| 74 | + |
| 75 | + |
| 76 | +# For using in-cluster postgres for catalog |
| 77 | +CATALOG_DEPLOY_ENABLED=true |
| 78 | +CATALOG_DEPLOY_CLUSTER_NAME=catalog-pg |
| 79 | + |
| 80 | + |
| 81 | +# For datadog metrics and logs |
| 82 | +DATADOG_ENABLED=false |
| 83 | +DATADOG_SITE=us5.datadoghq.com |
| 84 | +DATADOG_API_KEY= |
| 85 | +DATADOG_CLUSTER_NAME= #Something like <customer-name-enterprise> |
| 86 | + |
| 87 | + |
| 88 | +SAVE_VALUES_AS_SECRET=true |
0 commit comments