Update DFI containers under ThreatKB
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we're calling /usr/local/bin/pp-dev locally which is configured from the UI:
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
The issue does not name files or tests. Start by tracing where the UI configures the local /usr/local/bin/pp-dev invocation and locate the DFI container definitions. Done should mean the DFI containers are updated consistently with the intended ThreatKB configuration, with the relevant container workflow verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100