Skip to content

Conversation

@Igor-splunk
Copy link
Collaborator

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

  • Code changes adhere to the project's coding standards.
  • Relevant unit and integration tests are included.
  • Documentation has been updated accordingly.
  • All tests pass locally.
  • The PR description follows the project's guidelines.

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 20819976977

Details

  • 108 of 153 (70.59%) changed or added relevant lines in 18 files are covered.
  • 6 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.3%) to 86.069%

Changes Missing Coverage Covered Lines Changed/Added Lines %
pkg/splunk/enterprise/licensemanager.go 4 7 57.14%
pkg/splunk/enterprise/licensemaster.go 4 7 57.14%
pkg/splunk/enterprise/monitoringconsole.go 11 14 78.57%
pkg/splunk/enterprise/searchheadcluster.go 4 7 57.14%
pkg/splunk/enterprise/upgrade.go 4 7 57.14%
pkg/splunk/enterprise/clustermanager.go 26 31 83.87%
pkg/splunk/enterprise/events.go 8 13 61.54%
pkg/splunk/enterprise/standalone.go 3 8 37.5%
pkg/splunk/enterprise/indexercluster.go 8 14 57.14%
pkg/splunk/enterprise/clustermaster.go 12 21 57.14%
Files with Coverage Reduction New Missed Lines %
pkg/splunk/enterprise/events.go 6 63.33%
Totals Coverage Status
Change from base Build 20029264179: -0.3%
Covered Lines: 10775
Relevant Lines: 12519

💛 - Coveralls

@coveralls
Copy link
Collaborator

coveralls commented Jan 8, 2026

Pull Request Test Coverage Report for Build 20914773279

Details

  • 108 of 153 (70.59%) changed or added relevant lines in 18 files are covered.
  • 7 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.3%) to 86.061%

Changes Missing Coverage Covered Lines Changed/Added Lines %
pkg/splunk/enterprise/licensemanager.go 4 7 57.14%
pkg/splunk/enterprise/licensemaster.go 4 7 57.14%
pkg/splunk/enterprise/monitoringconsole.go 11 14 78.57%
pkg/splunk/enterprise/searchheadcluster.go 4 7 57.14%
pkg/splunk/enterprise/upgrade.go 4 7 57.14%
pkg/splunk/enterprise/clustermanager.go 26 31 83.87%
pkg/splunk/enterprise/events.go 8 13 61.54%
pkg/splunk/enterprise/standalone.go 3 8 37.5%
pkg/splunk/enterprise/indexercluster.go 8 14 57.14%
pkg/splunk/enterprise/clustermaster.go 12 21 57.14%
Files with Coverage Reduction New Missed Lines %
pkg/splunk/enterprise/cp.go 1 33.33%
pkg/splunk/enterprise/events.go 6 63.33%
Totals Coverage Status
Change from base Build 20029264179: -0.3%
Covered Lines: 10774
Relevant Lines: 12519

💛 - Coveralls

eventPublisher, _ := newK8EventPublisher(c, cr)

// Get event publisher from context, create one if not present
var eventPublisher *K8EventPublisher
Copy link
Collaborator

@kasiakoziol kasiakoziol Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could be

eventPublisher, _ = newK8EventPublisher(nil, cr)
if pub := ctx.Value(splcommon.EventPublisherKey); pub != nil {
		eventPublisher, _ = pub.(*K8EventPublisher)
	}

k8sevent.instance = &cmaster
k8sevent.Normal(ctx, "", "")

// Use client to avoid unused variable warning
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But why do we want to keep it then if it is unused?

scopedLog := reqLogger.WithName("ApplyLicenseMaster")
eventPublisher, _ := newK8EventPublisher(client, cr)

// Get event recorder from context
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could probably move it to a separate func that could be shared among all files

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.

3 participants