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