Skip to content

feat(splunk): add FILE_ACCESS violation support to Splunk TA API#19496

Draft
Stringy wants to merge 2 commits intogiles/enable-splunk-ta-testsfrom
giles/fam-violations-in-splunk-ta
Draft

feat(splunk): add FILE_ACCESS violation support to Splunk TA API#19496
Stringy wants to merge 2 commits intogiles/enable-splunk-ta-testsfrom
giles/fam-violations-in-splunk-ta

Conversation

@Stringy
Copy link
Contributor

@Stringy Stringy commented Mar 19, 2026

Description

The Splunk TA API silently dropped FILE_ACCESS violations — the type fell through to UNKNOWN and all file-specific data was lost.

  • Add FILE_ACCESS to ViolationType enum and FileAccessInfo message
  • Extract file paths, operation, metadata, hostname, and process info
  • Fall back to FileAccess.timestamp when Alert_Violation.time is nil

User-facing documentation

Testing and quality

  • the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
  • CI results are inspected

Automated testing

  • added unit tests
  • added e2e tests
  • added regression tests
  • added compatibility tests
  • modified existing tests

How I validated my change

change me!

The Splunk TA API silently dropped FILE_ACCESS violations — the type
fell through to UNKNOWN and all file-specific data was lost.

- Add FILE_ACCESS to ViolationType enum and FileAccessInfo message
- Extract file paths, operation, metadata, hostname, and process info
- Fall back to FileAccess.timestamp when Alert_Violation.time is nil

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci
Copy link

openshift-ci bot commented Mar 19, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@rhacs-bot
Copy link
Contributor

rhacs-bot commented Mar 19, 2026

Images are ready for the commit at d3945f5.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.11.x-370-gd3945f5c76.

@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

❌ Patch coverage is 91.66667% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.26%. Comparing base (775d656) to head (d3945f5).

Files with missing lines Patch % Lines
central/splunk/violations.go 91.66% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@                       Coverage Diff                        @@
##           giles/enable-splunk-ta-tests   #19496      +/-   ##
================================================================
- Coverage                         49.27%   49.26%   -0.01%     
================================================================
  Files                              2726     2725       -1     
  Lines                            205626   205636      +10     
================================================================
+ Hits                             101314   101316       +2     
- Misses                            96775    96782       +7     
- Partials                           7537     7538       +1     
Flag Coverage Δ
go-unit-tests 49.26% <91.66%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Stringy Stringy force-pushed the giles/fam-violations-in-splunk-ta branch from 0a85ba8 to d3945f5 Compare March 19, 2026 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants