splunk / splunk/contentctl

Include tags.atomic_guid and tags.required_fields into ESCU

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

Nobody has claimed this yet.

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

Description

It would help for these fields to be exposed to/included in the ESCU app.

See https://github.com/splunk/security_content/issues/2904.

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.

Research direction

Start by reading the referenced security_content issue 2904 and tracing how tags are exposed in the ESCU app. Identify the existing path for tag fields, then verify that tags.atomic_guid and tags.required_fields are included and visible in ESCU.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.