Skip to content

SplunkPy v2: add configuration file/stanza commands#45001

Draft
ilappe wants to merge 1 commit into
masterfrom
ilappe/CIAC-16603/add_command
Draft

SplunkPy v2: add configuration file/stanza commands#45001
ilappe wants to merge 1 commit into
masterfrom
ilappe/CIAC-16603/add_command

Conversation

@ilappe

@ilappe ilappe commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Related Issues

fixes: CIAC-16603

Description

  • Added the splunk-configuration-file-list command that lists the configuration (.conf) files available in a given Splunk app namespace.
  • Added the splunk-configuration-file-create command that creates a new, empty configuration (.conf) file.
  • Added the splunk-configuration-stanza-create command that creates a new stanza (configuration entry) in a Splunk .conf file, optionally with attributes.
  • Added the splunk-configuration-stanza-list command that lists the stanzas in a .conf file, or returns the content of a single stanza.
  • Added the splunk-configuration-stanza-update command that updates (upserts) attributes on an existing stanza in a Splunk .conf file.
  • Added the splunk-configuration-stanza-delete command that deletes a stanza from a Splunk .conf file (for example, transforms.conf), useful for cleaning up KV Store transformations that remain after deleting KV Store records.

@content-bot

Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@ilappe ilappe self-assigned this Jul 8, 2026
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/SplunkPy/Integrations/SplunkPyV2
   SplunkPyV2.py237145280%183, 186, 268, 294–295, 297–302, 304, 365–367, 421, 432, 574, 597, 608, 991, 997, 1000, 1131–1132, 1136, 1213, 1218, 1291–1292, 1320, 1334, 1344, 1347–1348, 1377–1378, 1431, 1550–1552, 1603, 1682, 1706–1707, 1789–1790, 1805–1810, 1836–1837, 1919–1924, 1926, 1930–1931, 2037, 2199–2200, 2282–2284, 2301–2302, 2337–2346, 2381–2382, 2384, 2402, 2449–2451, 2456–2457, 2463, 2466–2467, 2498–2499, 2507, 2565–2568, 2574–2576, 2580, 2637–2638, 2642–2644, 2646–2647, 2715, 2717, 2720–2723, 2726–2727, 2729–2731, 2748, 2754, 2793–2794, 2797–2798, 2801–2803, 2807, 2816, 2821, 2823–2824, 2829, 2831–2836, 2838–2839, 2844–2846, 2849–2853, 2858–2860, 2864–2866, 2869–2872, 2875–2877, 2881, 2887, 2889, 2892–2893, 2895–2896, 2898, 2901, 2931, 2969–2971, 2986–2987, 3004, 3046, 3048–3050, 3153, 3199, 3229, 3259, 3262–3263, 3268, 3291, 3398–3399, 3428–3429, 3432, 3434, 3442, 3444–3447, 3449–3457, 3459–3460, 3988, 4042, 4105, 4107, 4109, 4174–4181, 4183–4185, 4187–4192, 4194, 4239–4243, 4457, 4496, 4500, 4520, 4523, 4528–4533, 4535–4537, 4585, 4607, 4648, 4654, 4665, 4673, 4678, 4702–4703, 4742, 4753–4755, 4758–4759, 4761, 4776, 4801–4809, 4811, 4813–4816, 4818–4819, 4825, 4840, 4871–4874, 4877–4880, 4893–4896, 4940, 4981, 5022, 5051, 5053, 5058, 5077, 5081, 5112, 5148, 5161–5164, 5168–5169, 5173, 5187–5188, 5198, 5202, 5226–5228, 5234–5237, 5239, 5248, 5250, 5340–5342, 5373, 5375, 5383, 5385–5386, 5402–5403, 5406–5408, 5452–5453, 5458–5459, 5475–5479, 5482, 5484, 5490–5497, 5499–5500, 5502–5503, 5507–5515, 5517–5520, 5679–5680, 5683–5685, 5687, 5693–5701, 5706, 5712–5715, 5721–5724, 5728–5731, 5746, 5748–5749, 5751–5753, 5762, 5766–5773, 5780, 5797–5802, 5821–5828, 5832–5833, 5835–5840
TOTAL237145280% 

Tests Skipped Failures Errors Time
427 0 💤 0 ❌ 0 🔥 6.766s ⏱️

@content-bot

Copy link
Copy Markdown
Contributor

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

@content-bot

Copy link
Copy Markdown
Contributor

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅

@content-bot

Copy link
Copy Markdown
Contributor

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 5d49561c7653cf40

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants