feat: Please add CLI/Client support for testFindingsRefinement

Open
#214 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
api, cli

Research direction

Start by locating the existing CLI/client entry points for SecOps API endpoints and search for testFindingsRefinement support. Compare its request shape with the documented payload and investigate the reported INVALID_ARGUMENT response. Done means the endpoint can be invoked through the CLI/client for testing exclusions.

Written by the indexing model from the issue text.

Description

This API endpoint is used to test new exclusions without deploying them first to SecOps.
I tried calling it directly, but I keep getting a 400 INVALID_ARGUMENT error.

{
  "type": "DETECTION_EXCLUSION",
  "query": "...",
  "interval": {
    "startTime": "2026-01-29T15:28:13.975619Z",
    "endTime": "2026-04-29T15:28:13.975619Z"
  },
  "detectionExclusionApplication": {
    "curatedRules": [
      "projects/.../locations/eu/instances/.../curatedRules/ur_UUID"
    ]
  }
}

Thanks! 😁

Dominant language
Python
Stars
92
Forks
48
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/secops-wrapper

All issues in google/secops-wrapper

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.