Skip to content

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

Draft
catinspace-au wants to merge 1 commit into
mainfrom
fix/hunt-runner-reads-secrets
Draft

catinspace-au wants to merge 1 commit into
mainfrom
fix/hunt-runner-reads-secrets

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

The engine stores each alert destination's URL at alert-destinations/ in its secrets backend. The hunt runner reads it through scalo.secrets. The runner mounts only that directory of the engine's file backend read-only and sets DFE_ENGINE_SECRETS_PATH to match.

Remove the old mount of the engine's alert-destinations directory: it holds only metadata.

The engine creates the directory at startup. The runner waits for a healthy engine, so the subpath exists before the mount.

The engine stores each alert destination's URL at alert-destinations/<name> in its secrets backend. The hunt runner reads it through scalo.secrets. The runner mounts only that directory of the engine's file backend read-only and sets DFE_ENGINE_SECRETS_PATH to match.

Remove the old mount of the engine's alert-destinations directory: it holds only metadata.

The engine creates the directory at startup. The runner waits for a healthy engine, so the subpath exists before the mount.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant