feat: using .env file in github action

Even if this exposes secrets and config variables, since they should only be mock variables used for local testing it is not a security risk. For production always use a github actions environment with secrets and variables.

.env

@@ -0,0 +1,12 @@
+AWS_DEFAULT_REGION=us-east-1
+AWS_ENDPOINT_URL=http://localhost:4566
+
+REDSHIFT_MASTER_USER=dwh_user
+REDSHIFT_MASTER_PASSWORD=123456789Test
+REDSHIFT_DB_NAME=streaming_db
+REDSHIFT_CLUSTER_NAME=redshift-cluster
+REDSHIFT_TABLE_NAME=user_health_data
+
+KINESIS_STREAM_NAME=kinesis-stream
+
+S3_BUCKET_NAME=firehose-raw-data

.github/workflows/main.yaml

@@ -16,13 +16,6 @@ env:
   AWS_ENDPOINT_URL: http://localhost:4566
   AWS_ACCESS_KEY_ID: test
   AWS_SECRET_ACCESS_KEY: test
-  REDSHIFT_MASTER_USER: usernamered
-  REDSHIFT_MASTER_PASSWORD: RedPw1234
-  REDSHIFT_DB_NAME: streaming_db
-  REDSHIFT_CLUSTER_NAME: redshift-cluster
-  REDSHIFT_TABLE_NAME: user_health_data
-  KINESIS_STREAM_NAME: kinesis-stream
-  S3_BUCKET_NAME: firehose-raw-data
 
 jobs:
   cdk:
@@ -33,6 +26,13 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v3
 
+      - name: Load .env file
+        uses: xom9ikk/dotenv@v2
+        with:
+          path: ./
+          mode: ""
+          load-mode: strict
+
       - name: Setup Node.js
         uses: actions/setup-node@v3
         with:

.gitignore

@@ -120,7 +120,6 @@ celerybeat.pid
 *.sage.py
 
 # Environments
-.env
 .venv
 env/
 venv/