Skip to content

docs(#1753): add default values section to CVE package docs#1756

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/1753-document-cve-defaults
Open

docs(#1753): add default values section to CVE package docs#1756
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/1753-document-cve-defaults

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown

Add a "Default values" section to the CVE package documentation that lists each rule data key with its actual default value from rule_data.rego. This makes it easy for users to see the defaults without reading the source code.

Also relabel the existing example YAML block as "Example rule data (non-default)" and fix a typo in the example intro ("if" -> "of") to clearly distinguish customization examples from actual defaults.

Changes:

  • policy/release/cve/cve.rego: Updated METADATA annotations to
    include a defaults section with a link to rule_data.rego, and
    relabeled the existing example block.
  • antora/docs/*: Regenerated via make generate-docs.

Note: make test could not run in the sandbox (unshare not permitted). Tests were run directly via ec opa test and all 17 CVE tests passed.


Closes #1753

Post-script verification

  • Branch is not main/master (agent/1753-document-cve-defaults)
  • Secret scan passed (gitleaks — 71f6e6cf3f4e90d51f66207404e70034b501b3f7..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Add a "Default values" section to the CVE package documentation that
lists each rule data key with its actual default value from
rule_data.rego. This makes it easy for users to see the defaults
without reading the source code.

Also relabel the existing example YAML block as "Example rule data
(non-default)" and fix a typo in the example intro ("if" -> "of")
to clearly distinguish customization examples from actual defaults.

Changes:
- policy/release/cve/cve.rego: Updated METADATA annotations to
  include a defaults section with a link to rule_data.rego, and
  relabeled the existing example block.
- antora/docs/*: Regenerated via make generate-docs.

Note: make test could not run in the sandbox (unshare not permitted).
Tests were run directly via ec opa test and all 17 CVE tests passed.

Closes #1753
@fullsend-ai-review

fullsend-ai-review Bot commented Jun 19, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 10:44 AM UTC · Completed 10:54 AM UTC
Commit: 47d3320 · View workflow run →

@codecov

codecov Bot commented Jun 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
unit-tests 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
policy/release/cve/cve.rego 100.00% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fullsend-ai-review

Copy link
Copy Markdown

Looks good to me

Findings

Low

  • [stale_reference] policy/lib/rule_data/rule_data.rego:35 — Comment states # Used in release/cve.go but the actual file is policy/release/cve/cve.rego. No file named cve.go exists in the repository. This is a pre-existing issue not introduced by this PR.
    Remediation: Change the comment from # Used in release/cve.go to # Used in release/cve/cve.rego.

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge size: M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document default values for CVE rule data keys in user-facing docs

0 participants