Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 3 commits
- 3 files changed
- 3 contributors
Commits on Mar 11, 2025
-
chore: merge main into develop (#429)
backport changes after release 6.2
Commits on Mar 18, 2025
-
fix: Splunk metadata parsing logic: config stanzas must be loaded fro…
…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))
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v6.2.0...v6.2.1-beta.1