Repository navigation
Bring the library up to Vigil 2026.14, validate it with Vigil itself,… - #1
Merged
Merged
Conversation
… and add examples
The repo had drifted from the server it feeds. baselines/ was renamed to
playbooks/ in Vigil, so the Playbooks tab listed nothing; both automations said
action_kind: baseline, which the server refuses; one listened for alert_fired,
renamed to alert_sent in 2026.12, so it would have imported and never fired;
and every task used the pre-2026.13 {{ inputs.x }} marker and free-text
relevance:. Container Host Maintenance also could not run unattended: its step
needed a container name nothing supplied.
The cause was a second copy of Vigil's rules living here. The validators,
their tests and references/actions.json are gone; CI now checks out Vigil and
runs manage.py validate_community --strict, the same parsers the Community page
uses, plus the cross-file checks (slugs, uids, events, flat directories, no
home paths). It also re-runs weekly so a Vigil change that breaks a file shows
up here first.
Every existing file moves to the current layout with its uid kept, and new
examples cover what the task language can do now: relevant: probes, if/then
branches on step outputs, outcome:, hunts, a detection task with severity,
cves and boost, Linux and Windows patching, app_ensure, branching playbooks,
and alert-, approval- and schedule-triggered automations that work as a set.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… and add examples
The repo had drifted from the server it feeds. baselines/ was renamed to playbooks/ in Vigil, so the Playbooks tab listed nothing; both automations said action_kind: baseline, which the server refuses; one listened for alert_fired, renamed to alert_sent in 2026.12, so it would have imported and never fired; and every task used the pre-2026.13 {{ inputs.x }} marker and free-text relevance:. Container Host Maintenance also could not run unattended: its step needed a container name nothing supplied.
The cause was a second copy of Vigil's rules living here. The validators, their tests and references/actions.json are gone; CI now checks out Vigil and runs manage.py validate_community --strict, the same parsers the Community page uses, plus the cross-file checks (slugs, uids, events, flat directories, no home paths). It also re-runs weekly so a Vigil change that breaks a file shows up here first.
Every existing file moves to the current layout with its uid kept, and new examples cover what the task language can do now: relevant: probes, if/then branches on step outputs, outcome:, hunts, a detection task with severity, cves and boost, Linux and Windows patching, app_ensure, branching playbooks, and alert-, approval- and schedule-triggered automations that work as a set.