New content generator will set invalid detection types
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
https://github.com/splunk/contentctl/blob/e63ed1f073c7c453451ebd99f19c566389a4ebfd/contentctl/input/new_content_questions.py#L23-L30
and
https://github.com/splunk/contentctl/blob/e63ed1f073c7c453451ebd99f19c566389a4ebfd/contentctl/objects/enums.py#L4-L8
are inconsistent, which means it will let you set the detection type to, for instance, Investigation which will fail validation since it is not in the enum
Contributor guide
No contributing guide indexed for this repository
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
Read contentctl/input/new_content_questions.py lines 23-30 alongside contentctl/objects/enums.py lines 4-8. Align the new-content generator's detection-type choices with the enum values, then verify that generated content uses a valid detection type and passes validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100