Add worker env to docker deploy to silence any logs about picking def…

…ault values. (#5068)
airbytehq · Jul 29, 2021 · 196cbd5 · 196cbd5
1 parent 58e9f19
commit 196cbd5
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/.env b/.env
@@ -47,6 +47,8 @@ API_URL=/api/v1/
 INTERNAL_API_HOST=airbyte-server:8001
 LOG_LEVEL=INFO
 
+WORKER_ENVIRONMENT=docker
+
 # Cloud log backups. Don't use this unless you know what you're doing. Mainly for Airbyte devs.
 # If you just want to capture Docker logs, you probably want to use something like this instead:
 # https://docs.docker.com/config/containers/logging/configure/

diff --git a/docker-compose.yaml b/docker-compose.yaml
@@ -57,6 +57,7 @@ services:
       - AIRBYTE_VERSION=${VERSION}
       - AIRBYTE_ROLE=${AIRBYTE_ROLE:-}
       - TEMPORAL_HOST=${TEMPORAL_HOST}
+      - WORKER_ENVIRONMENT=${WORKER_ENVIRONMENT}
       - S3_LOG_BUCKET=${S3_LOG_BUCKET}
       - S3_LOG_BUCKET_REGION=${S3_LOG_BUCKET_REGION}
       - AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}
@@ -92,6 +93,7 @@ services:
       - AIRBYTE_VERSION=${VERSION}
       - AIRBYTE_ROLE=${AIRBYTE_ROLE:-}
       - TEMPORAL_HOST=${TEMPORAL_HOST}
+      - WORKER_ENVIRONMENT=${WORKER_ENVIRONMENT}
       - S3_LOG_BUCKET=${S3_LOG_BUCKET}
       - S3_LOG_BUCKET_REGION=${S3_LOG_BUCKET_REGION}
       - AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}