Skip to content

Fix NGSIEM stop_search parameter handling (Issue #1398)#1421

Open
jayy-77 wants to merge 3 commits intoCrowdStrike:devfrom
jayy-77:fix-ngsiem-stop-search-1398
Open

Fix NGSIEM stop_search parameter handling (Issue #1398)#1421
jayy-77 wants to merge 3 commits intoCrowdStrike:devfrom
jayy-77:fix-ngsiem-stop-search-1398

Conversation

@jayy-77
Copy link

@jayy-77 jayy-77 commented Jan 17, 2026

This commit fixes two related bugs in the stop_search method:

  1. Parameter Mismatch: The documentation specified 'id' parameter but the method only accepted 'search_id', causing user confusion.

  2. Missing Alias Support: Unlike get_search_status which accepts both 'id' and 'search_id' keywords, stop_search only accepted 'search_id'.

Changes:

  • Updated stop_search() to accept both 'id' and 'search_id' parameters
  • Improved documentation to clarify both parameters are supported
  • Fixed error message to reference 'id' instead of 'search_id'
  • Added comprehensive tests for both parameter variants
  • Enhanced existing integration tests to cover both approaches

This brings stop_search behavior in line with get_search_status and resolves the 'No content was received for this request' error that users encountered when using the 'id' parameter as documented.

Fixes #1398

jshcodes and others added 3 commits December 31, 2025 17:58
This commit fixes two related bugs in the stop_search method:

1. Parameter Mismatch: The documentation specified 'id' parameter but
   the method only accepted 'search_id', causing user confusion.

2. Missing Alias Support: Unlike get_search_status which accepts both
   'id' and 'search_id' keywords, stop_search only accepted 'search_id'.

Changes:
- Updated stop_search() to accept both 'id' and 'search_id' parameters
- Improved documentation to clarify both parameters are supported
- Fixed error message to reference 'id' instead of 'search_id'
- Added comprehensive tests for both parameter variants
- Enhanced existing integration tests to cover both approaches

This brings stop_search behavior in line with get_search_status and
resolves the 'No content was received for this request' error that
users encountered when using the 'id' parameter as documented.

Fixes CrowdStrike#1398
@jshcodes jshcodes changed the base branch from main to dev January 27, 2026 20:06
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.

NGSIEM stop_search giving 'No content was received for this request.'

2 participants