Skip to content

docs: warn that new Hive records are disabled by default#235

Merged
maximelb merged 1 commit into
masterfrom
docs/hive-disabled-by-default
May 21, 2026
Merged

docs: warn that new Hive records are disabled by default#235
maximelb merged 1 commit into
masterfrom
docs/hive-disabled-by-default

Conversation

@maximelb
Copy link
Copy Markdown
Contributor

Summary

Every new Hive record (D&R rules, FP rules, secrets, lookups, YARA sources, cloud sensors, AI skills, playbooks, …) is created disabled unless usr_mtd.enabled is set to true. Several Create/Update examples in the docs omit that, so a reader copying them ends up with a record that is stored but does nothing. Most painful for secrets and lookups, where the record is silently skipped by every consumer (outputs, D&R rules, etc.).

This PR:

  • Adds a prominent admonition at the top of config-hive/index.md documenting the disabled-by-default behavior and listing the three create-and-enable paths.
  • Fixes Create/Update examples across REST / Python / Go / CLI tabs in secrets.md and lookups.md to explicitly set enabled.
  • Updates the CLI examples in dr-rules.md, false-positives.md, 3-detection-response/index.md, the writing-testing-rules.md tutorial, and 9-ai-sessions/skills.md to use --enabled. (The REST/Python/Go tabs in those docs already set it.)
  • Updates the YARA Python SDK example to pass enabled=True.
  • Updates the "Create or update a rule" snippet in python-sdk.md to set enabled=True.

Dependency

The CLI --enabled / --disabled flag referenced in the updated CLI examples is being added in refractionPOINT/python-limacharlie#296. Until that lands, the REST/SDK patterns in this PR still apply, and the CLI path remains the existing two-step (set followed by enable). Holding this PR as draft until that one merges.

Test plan

  • npx markdownlint-cli2 — 308 files, 0 errors
  • Visual review of rendered admonition in config-hive/index.md
  • Verify each updated CLI example after python-limacharlie#296 ships

🤖 Generated with Claude Code

Every new Hive record (D&R rules, FP rules, secrets, lookups, YARA
sources, cloud sensors, AI skills, playbooks, …) is created disabled
unless usr_mtd.enabled is explicitly set to true. Several create/update
examples in the docs omit this and would silently produce a disabled
record — most painful for secrets and lookups, where the record is
stored normally but its consumers (outputs, D&R rules) skip it.

- config-hive/index.md: new top-level admonition listing the three
  create-and-enable paths (CLI --enabled flag, usr_mtd.enabled in body,
  SDK enabled=True / Enabled: &enabled).
- secrets.md and lookups.md: Create/Update examples now set enabled
  across REST, Python, Go, and CLI tabs.
- dr-rules.md, false-positives.md, detection-response/index.md,
  writing-testing-rules.md tutorial: CLI examples updated to include
  --enabled. (The REST/Python/Go tabs in those docs already set it.)
- yara.md: Python SDK example now passes enabled=True.
- python-sdk.md: "Create or update a rule" snippet now sets enabled.
- skills.md: CLI ai-skill set examples and Python SDK example now
  enable the skill at creation.

The CLI --enabled / --disabled flag referenced here is being added to
python-limacharlie in refractionPOINT/python-limacharlie#296. Until
that lands, the SDK/REST patterns still apply, and the CLI path
remains "set + enable" two-step.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@maximelb maximelb requested a review from steveatlc May 21, 2026 15:23
@maximelb maximelb marked this pull request as ready for review May 21, 2026 15:23
@maximelb maximelb merged commit 736bcf8 into master May 21, 2026
2 checks passed
@maximelb maximelb deleted the docs/hive-disabled-by-default branch May 21, 2026 15:23
@maximelb maximelb added the to-code-review Used to tag PRs that are force-pushed and will need to be reviewed after the fact. label May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

to-code-review Used to tag PRs that are force-pushed and will need to be reviewed after the fact.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant