opensearch-project / opensearch-project/security-analytics
[FEATURE] Id field should not be mandatory when creating custom rule
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 111
- Forks
- 111
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem?
In the create rule API, Id field is required as part of feature payload. User shouldn't have to pass this.
What solution would you like?
The Id field should be dropped from the requirement
What alternatives have you considered?
N/A
Do you have any additional context?

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue points to the create rule API and its custom-rule payload; start by tracing that endpoint's request validation and schema. Done means Id is no longer required when creating a custom rule, and the documented create-rule request reflects the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100