Allow for "Next Steps".

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli, tooling

Research direction

Start by tracing how contentctl currently defines and processes the next steps in the main detection file, then compare the existing macros and stories organization. Define how a separate configurable directory should represent environment-specific steps and confirm that detections can load it without losing the current behavior.

Written by the indexing model from the issue text.

Description

Making the next steps configurable with contentctl would save us a significant amount of time, especially since we're servicing multiple environments. To keep the main detection file clean and concise, these steps could be made configurable in a separate directory—similar to how macros and stories are organized.

Dominant language
Python
Stars
139
Forks
52
Avg merge
1h 16m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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 splunk/contentctl

All issues in splunk/contentctl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.