Skip to content
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

Scheme parameters not saving to correct /local/inputs.conf file #573

Open
koocies opened this issue Apr 5, 2024 · 0 comments
Open

Scheme parameters not saving to correct /local/inputs.conf file #573

koocies opened this issue Apr 5, 2024 · 0 comments

Comments

@koocies
Copy link

koocies commented Apr 5, 2024

Describe the bug
The local/inputs.conf information is not saved to the app that it belongs to. Rather, it saves the information in the app that splunk is currently open to (i.e. the search app). When I saved my configuration in the settings > input datas for my app I found the inputs.conf file was not created under my app. Searched with grep and I found the settings were saved in the splunk/etc/apps/search/local/inputs.conf

To Reproduce
Steps to reproduce the behavior:

  1. Have the random_numbers example app installed and splunklib 2.0.1
  2. Login to splunk and open the search app
  3. Go to settings > data inputs > "add new" for "Random Number
  4. Save settings
  5. less $SPLUNK_HOME/etc/apps/search/local/inputs.conf

Expected behavior
Expected the inputs.conf to be saved in the app that it belongs to.

Splunk (please complete the following information):

  • Version: 9.1.3
  • OS: Debian 6.1
  • Deployment: Local VM, enterprise, free edition

SDK (please complete the following information):

  • Version: 2.0.1
  • Language Runtime Version: Python 3.7
  • OS: Debian 6.1

Additional context
Add any other context about the problem here.

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

No branches or pull requests

1 participant