Skip to content

fix(fcs): add IOM limit validation, improve risks examples, and enhance error handling - #48

Open
eeran-cs wants to merge 2 commits into
CrowdStrike:mainfrom
eeran-cs:fix/fcs-validation-and-error-hints
Open

fix(fcs): add IOM limit validation, improve risks examples, and enhance error handling#48
eeran-cs wants to merge 2 commits into
CrowdStrike:mainfrom
eeran-cs:fix/fcs-validation-and-error-hints

Conversation

@eeran-cs

@eeran-cs eeran-cs commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • IOM list: add a --limit cap of 100 with a clear error message when exceeded (the API returns an error for larger values)
  • Risks list: correct and expand the --filter examples — severity values must be uppercase (HIGH, CRITICAL), and the cloud_provider FQL field is unreliable so examples now show --grep and jq alternatives; fix sort syntax from field.desc to field|desc
  • Error handling: add a filterHints map so HandleAPIError surfaces known filter field names on 400 responses; add human-readable keys to featureRequirements for the compliance 404 case

Test plan

  • falcon fcs iom list --limit 101 returns a clear error
  • falcon fcs risks list --filter "severity:'HIGH'" works; --filter "severity:'High'" documents the uppercase requirement
  • falcon fcs risks list --sort "severity|desc" works
  • HandleAPIError on a 400 from ContainerCombined includes the filter field hint
  • Compliance 404 returns the feature-not-provisioned message via the human-readable keys

- Add limit validation to IOM list command (max 100 items)
- Improve risks list command examples with correct severity format and filtering options
- Enhance error handling with filter hints for 400 responses
- Add legacy operation name keys for backward compatibility
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