-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathsample.env
41 lines (38 loc) · 1.18 KB
/
sample.env
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
DOCKER_HOST_IP=
BOOTSTRAP_SERVER=${DOCKER_HOST_IP}:9092
API_ENDPOINT=
DEPOSIT_TOPIC=
DEPOSIT_GROUP=
# Bucket name to deposit to (required for all destination types)
DEPOSIT_BUCKET_NAME=
DEPOSIT_KEY_NAME=
AWS_SESSION_TOKEN=
AWS_EXPIRATION=
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
HEADER_ACCEPT=
HEADER_X_API_KEY=
KAFKA_TYPE=
CONFLUENT_KEY=
CONFLUENT_SECRET=
# Defaults to true
KAFKA_ENABLE_AUTO_COMMIT=
# Defaults to 1000
KAFKA_AUTO_COMMIT_INTERVAL_MS=
# Defaults to 30000
KAFKA_SESSION_TIMEOUT_MS=
# MONGODB Variables
MONGO_IP=${DOCKER_HOST_IP}
MONGO_DB_NAME=ode
MONGO_DB_USER=admin
MONGO_DB_PASS=
MONGO_PORT=27017
MONGO_URI=mongodb://${MONGO_DB_USER}:${MONGO_DB_PASS}@${MONGO_IP}:${MONGO_PORT}/
MONGO_COLLECTION_TTL=7 # days
# Destination to deposit messages to
## Currently supported types are "s3" (Amazon S3 Bucket), "firehose" (Amazon Firehose), or "gcs" (Google Cloud Storage)
DESTINATION=
# Google Cloud Storage Variables
## path to service account key file (json format)
### If GOOGLE_APPLICATION_CREDENTIALS is blank, regardless of destination, it may cause issues when running the S3 depositor with Docker.
GOOGLE_APPLICATION_CREDENTIALS='./resources/google/sample_gcp_service_account.json'