Skip to content

Merge develop to feature/epic spl 290563#1708

Merged
sgontla merged 34 commits intofeature/epic_SPL-290563from
merge_develop_to_feature/epic_SPL-290563
Feb 19, 2026
Merged

Merge develop to feature/epic spl 290563#1708
sgontla merged 34 commits intofeature/epic_SPL-290563from
merge_develop_to_feature/epic_SPL-290563

Conversation

@sgontla
Copy link
Collaborator

@sgontla sgontla commented Feb 19, 2026

Description

Merge develop into kvservice epic branch

Key Changes

Merge develop into kvservice epic branch

Testing and Verification

Ran UT

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.

NGUYEN Duc Trung and others added 30 commits December 5, 2025 10:43
… as well as removing some uneccessary env vars added to the workflows.
…ement (#1640)

* Add CLA check

---------

Co-authored-by: igor.grzankowski <@splunk.com>
* Fix s3 regex

* Fix

---------

Co-authored-by: igor.grzankowski <@splunk.com>
…of exclusion rules, but the goal is to remove these as we work through them, as well as adding TLS support for metrics and webhooks (even if this won't yet be used)
…s-helm

ISSUE-1661 Add deployerNodeAffinity and deployerResourceSpec to SHC helm
* Use Recorder

* add publisher in test

* fix cluster master tests

* update verificationutils.go

* fix nil dereference

* Add check for replicas

* Remove unecessary tests

* allow apfw to update cr statusa

* GetEventPublisher as a common function

* Remove unused variable

---------

Co-authored-by: igor.grzankowski <@splunk.com>
- Update CLA check workflow to improve PR comment messages and conditions for signing the Code of Conduct.
- Adjusted conditions for triggering COC assistant based on PR comments.
* upgrade go version and ubi8 minimal version

* run integration tests for branch

* fix dockerfile golang version

* remove int test workflow branch
vuln-61143 upgrade opentelemtry-go from 1.33 to 1.40
* Add agents.md file

* review updates, add team members to .env reviewers
* Add License expired event

* Keep the removed events

* Mock the response / table tests

* fix

* fix

* use fakerecorder in tests

* debug

* inject publisher properly

* Add error

---------

Co-authored-by: igor.grzankowski <@splunk.com>
… and smart store (#1689)

* Adding events for passwords and secrets

* Adding events for CM, scaling ops, appfw and RF

* Refactoring

* Fixing syntax and tests

* Tests

* Tests

* Indexercluster tests

* util test

* shc/upgrade tests

* Match entire msg

---------

Co-authored-by: igor.grzankowski <@splunk.com>
Co-authored-by: igor.grzankowski <igorg@splunk.com>
- Opt-in deployment via config/default-with-webhook kustomize overlay
- Supports all Splunk Enterprise CRDs: ClusterManager, IndexerCluster, SearchHeadCluster, Standalone, - LicenseManager, MonitoringConsole
- Configurable timeouts via environment variables (WEBHOOK_READ_TIMEOUT, WEBHOOK_WRITE_TIMEOUT)
- TLS certificates managed by cert-manager with automatic CA injection

---------

Co-authored-by: Patryk Wasielewski <pwasiele@splunk.com>
fix: fix long execution time unit tests
@github-actions
Copy link
Contributor

github-actions bot commented Feb 19, 2026

CLA Assistant Lite bot: All contributors have NOT signed the COC Document


I have read the Code of Conduct and I hereby accept the Terms


7 out of 8 committers have signed the CLA.
@gabrielm-splunk
@Igor-splunk
@kasiakoziol
@kubabuczak
@rlieberman-splunk
@patrykw-splunk
@sgontla
@Nguyen Duc Trung
NGUYEN Duc Trung seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You can retrigger this bot by commenting recheck in this Pull Request

@github-actions
Copy link
Contributor

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


6 out of 8 committers have signed the CLA.
@gabrielm-splunk
@Igor-splunk
@kasiakoziol
@kubabuczak
@rlieberman-splunk
@sgontla
@Nguyen Duc Trung
@patrykw-splunk
NGUYEN Duc Trung seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You can retrigger this bot by commenting recheck in this Pull Request

@sgontla
Copy link
Collaborator Author

sgontla commented Feb 19, 2026

I have read the Code of Conduct and I hereby accept the Terms

@sgontla
Copy link
Collaborator Author

sgontla commented Feb 19, 2026

I have read the CLA Document and I hereby sign the CLA

@rlieberman-splunk
Copy link
Collaborator

Recheck

@rlieberman-splunk
Copy link
Collaborator

recheck

@sgontla sgontla merged commit a3cc821 into feature/epic_SPL-290563 Feb 19, 2026
23 of 29 checks passed
@sgontla sgontla deleted the merge_develop_to_feature/epic_SPL-290563 branch February 19, 2026 17:37
@github-actions github-actions bot locked and limited conversation to collaborators Feb 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

Comments