Skip to content

fix(compose): read alert destinations from the engine's secrets backend #363

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.

Sign up for GitHub

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

Merged
catinspace-au merged 1 commit into from
Nov 11, 2026
Merged

fix(compose): read alert destinations from the engine's secrets backend #363

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -502,15 +502,17 @@ services:
DFE_ENGINE_ENV: ${DFE_ENGINE_ENV:-production}
DFE_ENGINE_HUNTS_DIR: /app/config/deploy-repo/config/hunts
DFE_ENGINE_HUNTS_RULES_DIR: /app/config/deploy-repo/config/rules
DFE_ENGINE_SECRETS_PATH: /app/config/.secrets
OTEL_EXPORTER_OTLP_ENDPOINT: ${DFE_OTEL_EXPORTER_ENDPOINT:-}
OTEL_SERVICE_NAME: dfe-hunt-runner
volumes:
# Only the alert destinations from the engine's file secrets backend, never the whole root.
- type: volume
source: dfe-engine-config
target: /app/config/alert-destinations
target: /app/config/.secrets/alert-destinations
read_only: true
volume:
subpath: alert-destinations
subpath: .secrets/alert-destinations
- type: volume
source: dfe-engine-config
target: /app/config/deploy-repo/config
Expand Down
Loading