-
Notifications
You must be signed in to change notification settings - Fork 0
fix: add FLAIR2_ prefix to all ECS environment variable names #66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -54,9 +54,9 @@ resource "aws_ecs_task_definition" "api" { | |
| }] | ||
|
|
||
| environment = [ | ||
| { name = "REDIS_URL", value = var.redis_url }, | ||
| { name = "S3_BUCKET", value = var.s3_bucket_name }, | ||
| { name = "ENV", value = var.env } | ||
| { name = "FLAIR2_REDIS_URL", value = var.redis_url }, | ||
| { name = "FLAIR2_S3_BUCKET", value = var.s3_bucket_name }, | ||
| { name = "FLAIR2_ENVIRONMENT", value = var.env } | ||
| ] | ||
|
|
||
| secrets = [ | ||
|
|
@@ -144,9 +144,9 @@ resource "aws_ecs_task_definition" "worker" { | |
| ] | ||
|
|
||
| environment = [ | ||
| { name = "REDIS_URL", value = var.redis_url }, | ||
| { name = "S3_BUCKET", value = var.s3_bucket_name }, | ||
| { name = "ENV", value = var.env } | ||
| { name = "FLAIR2_REDIS_URL", value = var.redis_url }, | ||
| { name = "FLAIR2_S3_BUCKET", value = var.s3_bucket_name }, | ||
| { name = "FLAIR2_ENVIRONMENT", value = var.env } | ||
| ] | ||
|
Comment on lines
146
to
150
|
||
|
|
||
| secrets = [ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR description says these are consumed via
settings.redis_url/settings.s3_bucket, but the current backendSettingsmodel (backend/app/config.py) does not defineredis_urlors3_bucket, and a repo-wide search shows no other usage. Either add those settings fields in the backend (so these env vars actually take effect) or update the PR description / remove these env vars to avoid misleading configuration drift.