Skip to content

chore(release): merge develop into main #433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 19, 2025
Merged

chore(release): merge develop into main #433

merged 3 commits into from
Mar 19, 2025

Conversation

artemrys
Copy link
Member

No description provided.

sgoral-splunk and others added 3 commits March 11, 2025 16:12
backport changes after release 6.2
…m the system app (#432)

Method get_conf_stanzas internally calls
`$SPLUNK_HOME/bin/splunk cmd btool server list`
This command leads to accumulated output. It reads server.conf files
from all apps.
Such behaviour may lead to invalid results, if an app has different (not
supported) format in the conf file.

I suggest to change login and read configs only from the system app:
`$SPLUNK_HOME/bin/splunk cmd btool server list --app=system`
## [6.2.1-beta.1](v6.2.0...v6.2.1-beta.1) (2025-03-18)

### Bug Fixes

* Splunk metadata parsing logic: config stanzas must be loaded from the system app ([#432](#432)) ([1a5ee99](1a5ee99))
@artemrys artemrys requested a review from a team as a code owner March 19, 2025 08:05
@artemrys artemrys merged commit 464bfc2 into main Mar 19, 2025
40 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Mar 19, 2025
@srv-rr-github-token
Copy link
Contributor

🎉 This PR is included in version 6.2.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@srv-rr-github-token
Copy link
Contributor

🎉 This PR is included in version 6.3.0-beta.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants