Skip to content

fix: replace stale Phase 1 warning for dynamic pipelines#98

Merged
mostafa merged 1 commit into
mainfrom
fix/stale-dynamic-pipeline-warning
May 10, 2026
Merged

fix: replace stale Phase 1 warning for dynamic pipelines#98
mostafa merged 1 commit into
mainfrom
fix/stale-dynamic-pipeline-warning

Conversation

@mostafa
Copy link
Copy Markdown
Member

@mostafa mostafa commented May 10, 2026

Summary

Changes

  • main.rs (load_pipelines): Replace misleading "source resolution not yet supported" with dynamic source(s): <ids>
  • commands/eval.rs: Add note that rsigma eval does not resolve dynamic sources
  • commands/convert.rs: Add note that rsigma convert does not resolve dynamic sources
  • commands/fields.rs: Add note that rsigma fields does not resolve dynamic sources

Test plan

  • cargo test --workspace passes
  • cargo clippy --workspace --all-targets --all-features -- -D warnings passes
  • cargo fmt --all -- --check passes
  • Manual: rsigma eval with dynamic pipeline shows the new note instead of the old warning
  • Manual: rsigma resolve still resolves sources correctly (no change to resolve path)

The load_pipelines() warning "source resolution not yet supported" was
added during Phase 1 (PR #86) when source resolution did not exist.
Phases 2-3 (PR #87-#88) added full resolution in rsigma-runtime and
the daemon, but the shared warning was never updated. The daemon
resolves sources correctly after load_pipelines() runs, making the
warning misleading.

Replace the blanket warning with a neutral "dynamic source(s): ..."
info line in load_pipelines(), and add targeted notes in eval, convert,
and fields commands explaining that these sync-only commands do not
resolve dynamic sources and directing users to rsigma resolve or
rsigma daemon.
@mostafa mostafa merged commit 99c3956 into main May 10, 2026
10 checks passed
@mostafa mostafa deleted the fix/stale-dynamic-pipeline-warning branch May 10, 2026 22:09
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