fix: correct case details response key#257
Open
Haihan-Jiang wants to merge 1 commit into
Open
Conversation
Author
|
This is ready for review from my side. Could someone take a look when convenient? |
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
1 participant
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.
get_case_full_detailscurrently returns the case payload undercase_details:, with a trailing colon in the key name.This changes the key to
case_details, matching the surroundingcase_alertsandcase_commentskeys and making the response easier for callers to consume consistently.Tests:
python3 -m py_compile server/secops-soar/secops_soar_mcp/case_management.pygit diff --check