• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

splunk / splunk-operator / 22026813517
85%
main: 87%

Build:
Build:
LAST BUILD BRANCH: CSPL-4518
DEFAULT BRANCH: main
Ran 15 Feb 2026 12:39AM UTC
Jobs 1
Files 48
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

15 Feb 2026 12:29AM UTC coverage: 84.919% (-1.3%) from 86.191%
22026813517

Pull #1699

circleci

vivekr-splunk
Fix SDK to support legacy secret naming convention

This commit fixes the Platform SDK integration to work with existing
legacy secret naming conventions used by smoke tests and production
deployments.

Root Cause:
The SDK's secret resolver already supports legacy secrets! It looks
for source secrets at: splunk-{namespace}-secret (line 252 of resolver.go)

However, we were passing the wrong binding name format which caused
issues. The fix is simple: use a simpler binding name that allows
SDK to create properly versioned secrets while still finding the
legacy source secret.

Changes:
- pkg/splunk/enterprise/standalone.go: Changed secret binding name
  from "splunk-{crName}-{type}-secret" to "{crName}-credentials"

How It Works:
1. Operator calls ResolveSecret() with binding: "{crName}-credentials"
2. SDK looks for source secret: "splunk-{namespace}-secret" (legacy!)
3. SDK finds the legacy secret with all required keys
4. SDK creates versioned secret: "{crName}-credentials-v1"
5. SDK copies data from legacy secret to versioned secret
6. Returns ready secret reference

This ensures:
✅ Smoke tests work (use legacy: splunk-{namespace}-secret)
✅ Production deployments work (use legacy secrets)
✅ SDK versioning works (creates: {crName}-credentials-v1)
✅ Rolling updates work (SDK manages versions: v1, v2, v3)
✅ No code changes needed in tests or deployments

Tested Locally:
- Created test with legacy secret "splunk-test-namespace-secret"
- SDK successfully resolved it and created "test-standalone-credentials-v1"
- All keys copied correctly
- Secret marked as Ready

All enterprise tests pass:
✓ TestSecretAdapter_SDKMode
✓ TestSecretAdapter_SDKMode_SecretNotReady
✓ TestSecretAdapter_SDKMode_SecretVersioning
✓ TestApplyStandalone
✓ TestApplyStandaloneWithSmartstore
✓ TestApplyStandaloneSmartstoreKeyChangeDetection
✓ TestApplyStandaloneDeletion

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Pull Request #1699: [SPIKE] Platform SDK Integration for Standalone Controller

152 of 372 new or added lines in 4 files covered. (40.86%)

1 existing line in 1 file now uncovered.

11087 of 13056 relevant lines covered (84.92%)

28.61 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
6
90.48
-2.02% internal/controller/standalone_controller.go
20
84.0
pkg/splunk/enterprise/secret_adapter.go
70
91.12
-3.74% pkg/splunk/enterprise/configuration.go
124
46.99
-22.96% pkg/splunk/enterprise/standalone.go

Uncovered Existing Lines

Lines Coverage ∆ File
1
90.48
-2.02% internal/controller/standalone_controller.go
Jobs
ID Job ID Ran Files Coverage
1 22026813517.1 15 Feb 2026 12:39AM UTC 48
84.92
CircleCI Job
Source Files on build 22026813517
  • Tree
  • List 48
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • CircleCI Build #22026813517
  • Pull Request #1699
  • PR Base - develop (#21989948678)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc